Configuration Files (SAP Library - SAP Exchange Infrastructure (BC-XI))

Configuration Files

Use

The Java Proxy Framework (JPF) fetches server parameters from the exchange profile at runtime. Using these parameters, the JPF can determine server names from the System Landscape Directory, for example. In addition to the exchange profile, the JPF reads the following configuration files:

jpf.properties: A configuration file for test purposes (for example, you can divert copies of incoming and outgoing messages to a local file).

jpf.registry: Required to register the implementing classes for generated inbound beans (standalone: inbound interfaces) on the proxy server (standalone: on the XML inbound server).

jndi.properties: Required to localize the proxy beans if a standalone application calls an outbound proxy bean on the J2EE server.

logging.properties: Defines the settings for the logging of the JPF. The system gathers the initial settings from the exchange profile.

Note

For more information about the exchange profile, see the Configuration Guide.

The files jpf.properties, jpf.registry and logging.properties are expected in the work directory of the standalone application or of the J2EE server. If the root directory of the SAP J2EE Engine is <SERVER_HOME>, then the work directory of the J2EE server is located under the following path:

J2EE Work Directory

Server Type	Path
Standalone	<SERVER_HOME>\alone
Cluster	<SERVER_HOME>\cluster\server

Features

jpf.properties

Recommendation

Using the exchange profile, you can administrate the server landscape of the Exchange Infrastructure from a central point. If you change a server address, you can make the necessary changes for all components involved centrally. Therefore, you may only use the configuration file jpf.properties for test purposes, otherwise you will have to make these changes locally each time.

Each line in this file is structured as follows:

com.sap.aii.proxy.framework.<Parameter>=<Value>

Parameters in the jpf.properties file

Parameter	Value	Meaning
lcrHostname	<Host>	System Landscape Directory host. Only takes effect if information cannot be taken from the exchange profile.
lcrPortnumber	<Port>	System Landscape Directory port. Only takes effect if information cannot be taken from the exchange profile.
destination	http://<Host>: <Port>/sap/xi/engine/entry?action=execute&pipelineid=central	Overrides the address of the Integration Server inbound pipeline. <host> and <port> must be replaced by the host name and port number of the server on which the central Integration Engine is running. In other words, the physical address of the corresponding R/3 system. You must specify the client that was assigned the role of the Integration Server using the parameter destination.client.
destination.client	<Client>	Overrides the client that was assigned the role of the Integration Server. Example: 010.
requestFilename	<Filename.txt>	Diverts a copy of the SOAP message to the text outbound file <Filename.txt> for outbound messages. The system also saves the message payload as an XML file.
responseFilename	<Filename.txt>	Diverts a copy of the SOAP message to the text outbound file <Filename.txt> for inbound messages. The system also saves the message payload as an XML file.
senderName	<Name of a business system>	If you cannot reach the server specified using lcrHostname and lcrPortnumber, or if the standalone Java application is not entered on the server, enter the name of the sender business system using the parameter senderName. The JPF then does not try to determine the business system name using the technical ID and the host name.

jndi.properties

This file is only required in the outbound case, if a Java standalone application wants to use a proxy bean on the J2EE server. The file enables the application to locate the proxy bean by using the naming service of the J2EE server. It must be located in the work directory of the standalone application and contain the following entries:

java.naming.factory.initial=com.inqmy.services.jndi.InitialContextFactoryImpl

java.naming.provider.url=localhost

java.naming.security.principal=Administrator

java.naming.security.credentials=

Alternatively, you can also set these attributes directly in your application program.

logging.properties

Using this file, you configure logging at runtime. In the file logging.properties in the work directory, you can set different detailed loggings, using parameters. If no file of this type exists in the work directory, the system creates it and enters default settings when you first call the JPF. The default setting for logging information is NONE; this means that the system does not generate any logging information. In logging.properties, set the parameter severity to INFO, if required. As a result, the system writes a log in a file called ./log/default.trc in the work directory.

Caution

The file ./log/default.trc can become extremely large over time, because new entries are constantly being added to it. SAP recommends that you delete the contents of this file periodically.

Example of logging.properties

#Created by Java Proxy Framework
#Wed Feb 20 13:40:14 GMT+01:00 2002

.logs=log[defaultTrace]
.severity=INFO

/Applications.logs=log[applicationsLog]
/Applications.severity=INFO
/System.logs=log[systemLog]
/System.severity=INFO

formatter[DefaultTrace]=TraceFormatter
formatter[FullTrace].pattern=%24d (%p) [%t] %-44l %s: %m
formatter[FullTrace]=TraceFormatter

log[applicationsLog].formatter=ListFormatter
log[applicationsLog].pattern=./log/applications.log
log[applicationsLog]=FileLog

log[defaultTrace].formatter=formatter[DefaultTrace]
log[defaultTrace].pattern=./log/default.trc
log[defaultTrace]=FileLog

log[systemLog].formatter=ListFormatter
log[systemLog].pattern=./log/system.log
log[systemLog]=FileLog