Updating Portal Server Settings (RSPOR_T_PORTAL) 

Use

In table Connected Portals (technical name: RSPOR_T_PORTAL), you make various portal server settings.

The table is fully buffered. After maintaining this table, you need to initialize the table buffer on the BI application servers. This can be done in the SAP GUI with /$tab.

If you do not maintain the table, the associated menu entries for publishing in the BEx Web Application Designer and BEx Query Designer are deactivated.

Procedure

...

...

       1.      Start the transaction Table View Maintenance(transaction SM30).

       2.      Enter RSPOR_T_PORTAL under Table/View.

       3.      Choose Maintain.

       4.      To create a new entry, choose New Entries.

       5.      Maintain the connected portal:

○       RFC Destination: <RFC_DESTINATION>

To ensure integration between the BI system and portal, you have created a RFC destination with the naming convention <BI_SID>_<PORTAL_HOSTNAME>_<PORTAL_SID> in transaction SM59. Enter this RFC destination in the table so that the RFC destination can be recognized as a connected portal.

More information: Creating RFC Destinations in the ABAP System.

○       Name of the System: <SYSTEMALIAS>

The Name of the System field corresponds to the alias in the BI system. The alias is defined in the portal. The iViews in the portal can be clearly assigned to a BI system using the name of the system.

More information: Creating BI Systems in the Portal    

○       Standard Portal

You need to select exactly one portal in the table to define it as the default portal. The designated portal is used for selecting a folder in the BEx Broadcaster.

You can overwrite the standard portal using parameter ID RSPOR_DEFAULT_PORTAL (SET/GET parameter).

...

                                                  i.       On the SAP Easy Access screen, choose System → User Profile → Own Data.

                                                ii.       On the Parameter tab page, enter the parameter ID RSPOR_DEFAULT_PORTAL and the corresponding parameter value. The parameter value is the name of the RFC destination from the Portals Connectedtable.

○       URL prefix: <PORTAL_URL_PREFIX>

The URL Prefix field contains the URL to the portal, including protocol, host name and port, for example http://<portalserver><domain>:<port>.

○       KM metadata repository manager prefix: <KM_RM_METADATA_PREFIX>

This prefix, for example /bi_metadata, is defined while setting up the repository manager.

More information: BI Metadata Repository Manager  

○       BI CM repository prefix metadata/master data/InfoProvider data: <BI_DOCUMENT_PREFIX>

During the migration of BI documents to the CM repository, the system automatically enters the target CM repository for the relevant document class in table RSPOR_T_PORTAL. If you do not perform migration for this document class, or the entry is incorrect, enter the prefix (such as /bi_documents) under which you store the BI documents for metadata in the portal.

More information: BI Documents in Knowledge Management

○       Use SAP Export Lib (PDF)

Select this field if you want to active the Export Library for SAP NetWeaver BI in order to be able to export PDF, PostScript and PCL files from BEx web applications.

More information: Activating the Export Library for SAP NetWeaver BI.

○       Fonts Directory (PDF)

If you have selected the Use SAP Export Lib (PDF) field and intend to use other fonts in addition to the standard font, enter the file system path here to the folder that contains the required TrueType fonts on the portal server. (Example Windows: c:/windows/fonts). Note that this font path is the path of the Java server.

○       Use HTTPS for Adobe (PDF)

Select this field if you want to use die Adobe Document Services instead of the Export Library for SAP NetWeaver BI and want to use transfer protocol https for communication between the application server and the Adobe Document Services.

○       “My Portfolio” Directory

       2.      Save your entries.

For Information Broadcasting, you need to maintain the Standard Portal, URL Prefix and KM Metadata Repository Manager Prefix fields. The BEx Broadcaster requires this information to provide the input help feature for the folders in Knowledge Management (KM folders). To store online links to queries or BEx Web applications in Knowledge Management, the prefix for the BI Metadata Repository Manager is needed. These fields are not required for other application cases.

Check

Start the BEx Web Application Designer. In the menu Web Template  →  Publish, the entry has been activated with To Portal.