List of Profile Parameters
The following lists show the parameters that would be relevant in a customer installation, along with a brief explanation.
When you compare these lists with the complete exchange profile, you can see that most of these parameters are in fact for SAP internal use only, and therefore should not be changed during a customer installation.
Parameters in section Default
Name |
Description |
com.sap.aii.docu.url |
Points to the root URL where the tool documentation files are installed (if no documentation is available use "null"). |
com.sap.aii.docu.languages |
Comma-separated list of the language codes of the installed external tool documentation. |
Parameters in section Connections
Name |
Description |
com.sap.aii.connect.repository.name com.sap.aii.connect.repository.httpport com.sap.aii.connect.repository.httpsport com.sap.aii.connect.repository.rmiport com.sap.aii.connect.repository.mshost com.sap.aii.connect.repository.mshttpport com.sap.aii.connect.repository.mshttpsport |
Connection parameters of the repository server: ● Host name ● HTTP port number ● HTTPS port number (optional) ● RMI port number (RMI is used for communication with the WebStart Client) ● SCS message server host name, HTTP port, and HTTPS port (for high-availability environments only) |
com.sap.aii.connect.directory.name com.sap.aii.connect.directory.httpport com.sap.aii.connect.directory.httpsport com.sap.aii.connect.directory.rmiport com.sap.aii.connect.directory.mshost com.sap.aii.connect.directory.mshttpport com.sap.aii.connect.directory.mshttpsport |
Connection parameters of the directory server: ● Host name ● HTTP port number ● HTTPS port number (optional) ● RMI port number (RMI is used for communication with the WebStart Client) ● SCS message server host name, HTTP port, and HTTPS port (for high-availability environments only) |
com.sap.aii.connect.landscape.name com.sap.aii.connect landscape.httpport com.sap.aii.connect landscape.httpsport |
Connection parameters of the System Landscape Directory server (listening for WBEM requests). WBEM is the communication standard under CIM. They are both defined by the Distributed Management Task Force (for more information, see www.dmtf.org). |
com.sap.aii.connect.cr.name com.sap.aii.connect.cr.httpport com.sap.aii.connect.cr.httpsport |
Connection parameters of the Component Repository (usually equivalent to the System Landscape Directory). |
com.sap.aii.connect.rwb.name com.sap.aii.connect.rwb.httpport com.sap.aii.connect.rwb.httpsport |
Connection parameters of the Runtime Workbench. |
com.sap.aii.connect.rwb.r3.sysnr com.sap.aii.connect.rwb.r3.client com.sap.aii.connect.rwb.r3.mshost com.sap.aii.connect.rwb.r3.r3name com.sap.aii.connect.rwb.r3.group |
Connection parameters for the ABAP part of the Runtime Workbench. |
com.sap.aii.connect.integrationserver.name com.sap.aii.connect.integrationserver.httpport com.sap.aii.connect.integrationserver.httpsport |
Connection parameters of the Integration Server. |
com.sap.aii.connect.integrationserver.r3.httpport com.sap.aii.connect.integrationserver.r3.httpsport com.sap.aii.connect.integrationserver.r3.sysnr com.sap.aii.connect.integrationserver.r3.client com.sap.aii.connect.integrationserver.r3.mshost com.sap.aii.connect.integrationserver.r3.r3name com.sap.aii.connect.integrationserver.r3.group |
Connection parameters for the ABAP part of the Integration Server. |
com.sap.aii.connect.secure_ connections |
List of components that use SSL communication instead of plain HTTP. |
Parameters in section IntegrationBuilder
Name |
Description |
com.sap.aii.ib.client.login.languages |
Comma-separated list of installed languages. |
com.sap.aii.ib.client.content.languages |
Comma-separated list of languages used for content documentation. |
com.sap.aii.ib.server.connect.webas.r3.client
com.sap.aii.ib.server.connect.webas.r3.ashost
com.sap.aii.ib.server.connect.webas.r3.sysnr
com.sap.aii.ib.server.connect.webas.r3.usefastrfc
com.sap.aii.ib.server.lockauth.activation
com.sap.aii.ib.util.server.auth.activation |
JCo connection from the J2EE engine to "its" ABAP instance (used by the locking service): ● SAP client (see JCo documentation of property jco.client.client). Filled with "000" during installation. ● SAP application server (see JCo documentation of property jco.client.ashost). Automatically filled during installation. ● SAP system number (see JCo documentation of property jco.client.sysnr). Automatically filled during installation. ● Determines whether fast RFC should be used for connecting to the ABAP part of the SAP Web AS. ● Activates locking (should always be "true"). ● Activates data-dependent authorizations. |
Parameters in section IntegrationBuilder.Repository
Name |
Description |
com.sap.aii.repository.serviceuser.name com.sap.aii.repository.serviceuser.pwd com.sap.aii.repository.serviceuser.language com.sap.aii.repository.serviceuser.certificate |
This is the service user (for example, PIREPUSER) used by the Integration Repository. |
com.sap.aii.repository.mapping.additionaltypes |
Besides the standard mapping types like "class" for Java mapping programs or "xsl" for XSLT programs, you can register additional mapping types of SAP partners. These additional mapping types enable you to call mapping programs of SAP partners, by calling a BAdI registered under the same mapping type. In the Integration Builder, you can select the additional mapping types in the Interface Mapping Editor when you create an interface mapping. You can enter a link to a mapping program of an SAP partner in the Interface Mapping, which is passed to the BAdI during the execution. You have to specify a key and a caption for an additional mapping type. The key field is restricted to 20 characters and should only contain the characters a,...,z and A,...,Z, the numbers 0,...,9, and the underscore "_". The caption should not exceed 25 characters. The caption is separated from the key by "|". Different additional mapping types are separated by ";".
PA_TYPE|Partner Mapping;pa_trafo|Partner Transformation
Use the value "none", if no additional mapping types are used. |
com.sap.aii.ibrep.core.cms.enableClTransport |
Specifies whether the transport of change lists with CMS can be triggered from within the user interface. |
com.sap.aii.ibrep.core.cms.enableTransportWizard |
Specifies whether the CMS transport can be triggered within the export wizard. |
com.sap.aii.repository.serviceuser.name.cms |
Are used to override user and password that are used for the communication from PI to CMS. |
com.sap.aii.repository.serviceuser.pwd.cms |
Parameters in section IntegrationBuilder.Directory
Name |
Description |
com.sap.aii.directory.serviceuser.name com.sap.aii.directory.serviceuser.pwd com.sap.aii.directory.serviceuser.language com.sap.aii.directory.serviceuser.certificate |
This is the service user (for example, PIDIRUSER) used by the Integration Directory. |
com.sap.aii.ibdir.core.cms.enableClTransport |
Specifies whether the transport of change lists with CMS can be triggered from within the user interface. |
com.sap.aii.ibdir.core.cms.enableTransportWizard |
Specifies whether the CMS transport can be triggered within the export wizard. |
com.sap.aii.directory.serviceuser.name.cms |
Are used to override user and password that are used for the communication from PI to CMS. |
com.sap.aii.directory.serviceuser.pwd.cms |
Parameters in section IntegrationServer
Name |
Description |
com.sap.aii.integrationserver.serviceuser.name com.sap.aii. integrationserver.serviceuser.pwd com.sap.aii. integrationserver.serviceuser.language com.sap.aii. integrationserver.serviceuser.certificate |
This is the service user (for example, PIISUSER) used by the Integration Server. |
Parameters in section IntegrationServer.MappingRuntime
Name |
Description |
com.sap.aii.mapping.transformerFactory |
Customers may want to use a different XML/XSLT engine such as XALAN/Xerces for processing mappings. |
com.sap.aii.mapping.parserFactory |
See above. |
Parameters in section ApplicationSystem
Name |
Description |
com.sap.aii. applicationsystem.serviceuser.name com.sap.aii. applicationsystem.serviceuser.pwd com.sap.aii. applicationsystem.serviceuser.language com.sap.aii. applicationsystem.serviceuser.certificate |
This is the service user (for example, PIAPPLUSER) used by application systems. This user should exist on the main Integration Server and also be associated with the appropriate RFC destination on application systems using SM59. |
Parameters in section RuntimeWorkbench
Name |
Description |
com.sap.aii.rwb.serviceuser.name com.sap.aii.rwb.serviceuser.pwd com.sap.aii.rwb.serviceuser.language com.sap.aii.rwb.serviceuser.certificate |
This is the service user (for example. PIRWBUSER) used by the Runtime Workbench. |
com.sap.aii.rwb.server.centralmonitoring.r3.ashost com.sap.aii.rwb.server.centralmonitoring.r3.client com.sap.aii.rwb.server.centralmonitoring.r3.sysnr com.sap.aii.rwb.server.centralmonitoring.httpport com.sap.aii.rwb.server.centralmonitoring.name com.sap.aii.rwb.server.centralmonitoring.r3.mshost com.sap.aii.rwb.server.centralmonitoring.r3.r3name com.sap.aii.rwb.server.centralmonitoring.r3.group |
SAP NetWeaver application server on which the central PMI, central CCMS, and central Alert Server run. Required for JCo connections and HTTP connections to the monitoring server. |
Parameters in section AdapterFramework
Name |
Description |
com.sap.aii. adapterframework.serviceuser.name com.sap.aii. adapterframework.serviceuser.pwd com.sap.aii. adapterframework.serviceuser.language com.sap.aii. adapterframework.serviceuser.certificate |
This user (for example, PIAFUSER) is used by the Adapter Framework when connecting to other servers. |