Creating BW Systems in the Portal 

Use

The BW system must be set up in the portal so that content from SAP BW can be displayed in it. The system is entered into the Portal System Landscape Directory.

This setting is required for all integration scenarios (see Integration from the Viewpoint of Administrators and Authors).

Procedure

       1.      Log on to the portal.

       2.      Start the iView System Administration ® System Configuration ® System Landscape.

The systems are maintained with the Portal Content Studio. For more information about using the Portal Content Studio, see Integration Using the Portal Content Studio.

       3.      Choose New ® System in the context menu of the Portal Catalog.

       4.      Depending on the system landscape, choose either the R/3 with Load Balancing (SAP_R3_LoadBalancing) or Dedicated Application Server for R/3-System (SAP_R3_Dedicated) as a template.

       5.      Maintain the most important properties with the property category Display All.

¡        Logon method: SAPLOGONTICKET or UIDPW

¡        Type of user assignment: admin,user

¡        Logical system name:  <SID>CLNT<MANDANT>

This is the recommended convention for logical system names, consisting of the system ID and the client.

¡        Remote host type: 3

¡        SAP client: <CLIENT>

¡        SAP system ID (SID) (R/3 name): <SID>

¡        System type: SAP_BW

¡        System name: <SID>CLNT<MANDANT>

¡        WAS description: <DESCRIPTION>

¡        WAS host name: <HOSTNAME>:<PORT>

¡        WAS path: /sap/bw/bex

¡        WAS protocol: http or https

All system entries refer to the BW system.

You can determine the WAS hostname, WAS path and WAS protocol settings using function module RSBB_URL_PREFIX_GET (transaction code SE37).

To use Drag&Relate, maintain the following properties:

¡        Admin User-ID (DQE): <USER>

¡        Admin password (DQE): <PASSWORD>

 

The Distributed Query Engine (DQE) executes the requests to the BW system with the Admin User above.

If you are using R/3 with Load Balancing (SAP_R3_LoadBalancing), you must also maintain the following properties:

¡        Group: <GROUP>

¡        Message server: <MESSAGE_SERVER>

¡        Server port: <SERVER_PORT>

The server port is frequently maintained by system administrators on the local PC in the c:\windows\system32\drivers\etc\services file. The server port of the system is entered into the file as sapms<SID>.

If you are using a Dedicated Application Server for R/3 System (SAP_R3_Dedicated), you must also maintain the following properties:

¡        Application host: <HOSTNAME>

¡        Gateway host: <HOSTNAME>

¡        Gateway service: <SERVICE>

¡        SAP system number: <NUMBER>

The report Maintaining Settings for Integration into SAP Enterprise Portal (RSPOR_SETUP) determines most of the mandatory values for the above properties automatically.

       6.      Maintain an alias for the system in the System Aliases view.

A system alias in the format <SID>CLNT<CLIENT> must exist, where <SID> is the system ID and <CLIENT> is the client for the system. CLNT is predefined. In addition to the system alias in the format above, you can also maintain other system aliases.

During integration of SAP BW 3.5 and SAP EP 6.0, the system alias in SAP 3.5 must be entered into the table Connected Portals (see Maintaining Portal Server Settings for EP 6.0).

In order to use the example role Business Explorer (see Calling Content from the SAP BW in the Enterprise Portal), an alias must be maintained in SAP_BW. Multiple system aliases can be defined for a BW system.

       7.      Save your entries.

Check

With the Connection Tests you can check the settings above. However, only the SAP Web AS Connection and the Connection Test for Connectors.