SAP RFC Parameter (Sun N1 Advanced Architecture for SAP Solutions 5.2.1 User's Guide)

Sun N1 Advanced Architecture for SAP Solutions 5.2.1 User's Guide

SAP RFC Parameter

Purpose: Settings for SAP RFC communication.
Menu: Administration ⇒ Deployer ⇒ Customizing
Tasks for an initial basic setup: Mandatory

While creating or removing SAP Application Instances, the existing Logon and RFC Servers Groups of the SAP System might be modified. The action of creating adds the instance to the SAP Systems Logon or RFC Server Groups. The action of removing deletes the instance from the SAP Systems Logon or RFC Server Groups.

N1 AA uses the RFC parameters to communicate with the SAP system. This is true for all SAP systems in your N1 AA landscape. You have to provide the same user ID and password in every SAP system.

Table 5–1 SAP RFC Parameters


Parameter	Description	Example value
`none.deployment.saprfc.client`	Logon client for RFC communication.	000
`none.deployment.saprfc.password`	Logon password for RFC communication. Password is stored encrypted in the N1 AA database.	n1aapwd
`none.deployment.saprfc.timeout`	Timeout value, in minutes, for RFC communication	2
`none.deployment.saprfc.user`	User for RFC communication. SAP user type `communications (CPI-C)` is sufficient.	n1aauser

Note –

Regarding the previous parameters. You can add additional optional parameters by replacing none with servergroup. For example, servergroup.deployment.saprfc.user, where servergroup is the name of an existing server group. This overwrites the parameter value within the specified server group.