Show TOC

List of Profile ParametersLocate this document in the navigation structure

Use

The following sections describe parameters that are relevant for a customer installation.

Note

The parameters that are not in the exchange profile will not normally need to be changed in a production installation.

Parameters in section AdapterFramework

Name

Description

com.sap.aii.adapterframework.serviceuser.name

com.sap.aii.adapterframework.serviceuser.pwd

com.sap.aii.adapterframework.serviceuser.language

This user (for example, PIAFUSER) is used by the Adapter Framework when connecting to other servers.

Parameters in section ApplicationSystem

Name

Description

com.sap.aii.applicationsystem.serviceuser.name

com.sap.aii.applicationsystem.serviceuser.pwd

com.sap.aii.applicationsystem.serviceuser.language

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 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 (more information: 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.

More information: Syntax of Parameter for Secure Communication

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 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. The first language in this list is used as default content language.

This list also specifies the set of possible target languages for the manual translation of texts written with the object editor or the documentation editor.

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.util.server.lock.activation

com.sap.aii.ib.util.server.auth.activation

JCo connection from AS Java to its ABAP instance (used by the locking service):

  • SAP client (refer to JCo documentation of property jco.client.client ). Filled with "000" during installation.

  • SAP application server (refer to JCo documentation of property jco.client.ashost ). Automatically filled during installation.

  • SAP system number (refer to JCo documentation of property jco.client.sysnr ). Automatically filled during installation.

  • Determines whether fast RFC should be used for connecting to AS ABAP.

  • Activates the locking service (should always be "true").

  • Activate data-dependent authorizations.

com.sap.aii.ib.server.acl.enable

com.sap.aii.ib.server.adv.acl

This property controls whether the advanced ACL permissions are checked for the current server.

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

This is the service user (for example, PIREPUSER) used by the Enterprise Services 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 Enterprise Services Repository, 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 ";".

Example

PA_TYPE|Partner Mapping;pa_trafo|Partner Transformation

Note

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

com.sap.aii.repository.serviceuser.pwd.cms

Override the user and password that are used for the communication from PI to 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

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

com.sap.aii.ibdir.core.originalLanguage

Specifies the original language of a software component version. The default value is EN.

If this property is missing in the exchange profile, EN is automatically used as original language.

Cache Refresh

When the cache is refreshed, the configuration data maintained in Integration Directory is synchronized with the configuration data maintained by the runtime components. Each runtime component in PI - ABAP Integration Server has its own database for storing configuration data. The runtime components include Java Adapter Engine, CPA cache, Java Message Mapping Cache, and Java Value Mapping Cache.

The cache can be refreshed using the following methods:

  • Delta Cache Refresh

    Delta Cache Refresh analyzes the changes made in Integration Directory and sends them as an xml message to the runtime components (cache consumers). The runtime components then apply the changes by adding or removing configuration objects.

  • Full Cache Refresh

    Full Cache Refresh sends the complete set of configuration objects in one xml document to the runtime components.

    Note

    Performing a full cache refresh may take long time, and no messages can be processed during a full cache refresh. For these reasons, a full cache refresh may require a downtime of your production operation.

By default, cache refresh has the following settings:

  • Statistics files are created for full cache refresh only

  • Statistics files are written to the global engine's directory at . /xi/directory_server/cache_refresh

  • Temporary files are saved in the temporary folder of the Java node.

The parameters for cache refresh are described in the section below.

Name

Description

com.sap.aii.ibdir.server.cache.statistic

Creates a statistics file.

Possible values:

  • on, yes, always

    Always create a statistics file.

  • off, no, never

    Do not create a statistics file.

  • C

    Create a statistics file for cache mode C (delta cache)

  • F

    Create a statistics file for full cache refresh.

  • N

    Create a statistics file for cache notification.

  • TF

    "Test full" mode

The default value is F,TF (full cache refresh only).

com.sap.aii.ibdir.server.cache.directory

Specify where the statistic files are written.

Use the following prefixes:

  • %global%

    for .../SYS/global/xi/directory_server/

  • %temp%

    for .../j2ee/cluster/serverN/temp/

The default value is %global%/cache_refresh/ .

com.sap.aii.ibdir.server.cache.tempFiles.directory

Specify where the temporary files are written.

Use the following prefixes:

  • %global%

    for .../SYS/global/xi/directory_server/

  • %temp%

    for .../j2ee/cluster/serverN/temp/

The default value is %temp%/cache_refresh/ .

com.sap.aii.ibdir.server.cache.onhold

Allows you to perform a full cache refresh.

It is recommended that you choose value F to deactivate the option to perform a full cache refresh.

Parameters in section IntegrationServer

Name

Description

com.sap.aii.integrationserver.serviceuser.name

com.sap.aii.integrationserver.serviceuser.pwd

com.sap.aii.integrationserver.serviceuser.language

This is the service user (for example, PIISUSER) used by the Integration Server.

Parameters in section RuntimeWorkbench

Name

Description

com.sap.aii.rwb.serviceuser.name

com.sap.aii.rwb.serviceuser.pwd

com.sap.aii.rwb.serviceuser.language

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.