Portal System Object Properties SAP System with Load Balancing Template

How to create a System Object with SAP System with Load Balancing Template
 

Purpose:

This document will outline where to obtain each parameter for the Connector definition in the portal system object. This document refers to the system object of type 'SAP system with load balancing'. This is the most common system template used for portal connectivity to the backend.
Note: While some connector properties such as SID and Client are relevant for all types of integration with the backend, the Connector Test for Connectors is only relevant for JCO/RFC connections. This test is not relevant for application integration scenarios - i.e. integration of BW Reports, BSPs, IACs, Transactions using SAP GUI for Windows or SAP GUI for HTML, WebDynpro for Java or WebDynpro for ABAP.

Overview:

To integrate backend content into the Enterprise Portal, a System Object needs to be created in the Portal System Landscape. The connector properties of the system object, enables connection via RFC/JCO calls to the backend system. This connection type is primarily used in connecting the UWL to a workflow system. It is also used to connect the Portal to non-SAP systems.

Obtaining the Property Definitions

Group:

This is referring to the logon/Server group name which is assigned to a number of instances. When users log on, they connect to these groups and are automatically logged on to the instance with the best response time. This is mandatory for a message server connection. To find the Logon Group, you need to go to transaction SMLG.



You need to make sure the Logon Group is valid. If you double click on the Group and from the resulting pop-up click the tab Attribute, you will have the option to Test the Group. This must pass or the Connector will not work in the Portal.

Logical system name:

This is always in the form <SystemID>CLNT<Client>
The info can be got from the details tool bar of the R3 session:



In the above example, what should be maintained is Y55CLNT800

Message Server:

The task of the message server is to inform all the servers (instances) belonging to a SAP System of the existence of the other servers. It can also be contacted by other clients (for example, SAPlogon, RFC clients with load balancing) to get information about load balancing. You must maintain the message server name in order for the system object to establish a connection to this. You can obtain the message server name via the transaction SMMS. This is the Message Server Monitor.



From the Message Server Monitor, Goto -> Parameters -> Display. The Message Server property should be ‘server host (FQN)’ to indicate the Fully Qualified Domain Name of the MS.

Remote Host Type:

This describes the type of remote system you are connecting to. In most cases this will be 3, representing an R3 system. Use E for external and 2 for an R2 system.

SAP Client:

The SAP Client will be known from the Logical System Name. In the above example, this would be 800.

SAP System ID (SID):

Again, this should be the same as defined in the Logical System Name, <SID>.

Server Port:

This is referring to the message server port. Due to this the property is mandatory for a message server connection. It is obtained again from transaction SMMS and the parameters section. See the previous screenshot.

SAP System Number:

This is also referred to as the Instance number. The value can be found via the transaction RZ10:



You will need to enter the name of the start profile (instance) via the Profile drop-down. Then make sure the Extended maintenance radio button is check and then choose Display.



The parameter SAPSYSTEM will indicate the System number or Instance number.

System Type:

This will refer to the type of system you are to connect to. The options are SAP_R3, SAP_BW or SAP_CRM.

Trace Mode:

If you wish for an RFC trace to be recorded, you can enable this by setting this property to 1. The default value is 0 (disabled). The RFC trace can be retrieved in the backend transaction: ST11
For more information see SAP Note  532918 RFC trace generation scenarios.

SNC Information:

Secure Network Communication (SNC).

If your portal iView will be retrieving sensitive data (user information, credit card details etc) from the abap or backend system , it is strongly advised this is secured with SNC. SNC is only available where the iViews connect to the ABAP system using RFC or JCO.