This documents describes some J2EE service properties for which changes may be required.
You may need to change the following properties of the service SAP XI AF Adapter: XI:
These properties determine how long asynchronous messages are to be kept in the database before they can be deleted or archived. The default value is 30 days.
If you expect a message load that exceeds the maximum database size within 30 days, you must reduce this value before the first messages are sent, because changes to this value will only affect new messages.
You may need to change the following properties of the service SAP XI AF Messaging:
The headers of synchronous messages are kept in main storage for monitoring purposes. Therefore, the main storage available to the J2EE Engine may quickly fill up in scenarios with very large synchronous messages or with large numbers of small synchronous messages. This in turn may lead to a Java OutOfMemoryError.
This property determines how often the headers of synchronous (error-free) messages are to be removed from main storage.
The Adapter Engine messaging system delivers messages to enterprise Java beans (EJBs) and tries to read these EJBs from the JNDI when starting the SAP XI AF Messaging service.
This property determines how often and at what time intervals the messaging service tries to find the EJBs.
Since EJBs are part of J2EE applications and therefore only started after the J2EE services, it may take some time before they are available.
By default, the messaging service tries to find the EJBs 10 times, with an interval of one minute each time. Therefore, if it takes longer than 10 minutes to start up the applications in the J2EE Engine, the EJBs cannot be found during startup. This in turn leads to error code HTTP 503 (The requested application, AFW, is currently unavailable) when messages are sent to the Adapter Engine.
In this case, you must either increase the number of retries or the time interval for all connections of this property.
You may need to change the following properties of the service SAP XI AF Cache:
The Adapter Engine registers itself automatically in the System Landscape Directory (SLD) at startup. By default, the name of the host without the domain name is used for this purpose. If you want to register the host of a (non-)central Adapter Engine with full host and domain names in the SLD, you can use this property to overwrite the name that is used for SLD registration.
You have to change these properties in cross-domain scenarios, so that the Adapter Engine can be reached from all involved network domains.
You may need to change the following property of the service SAP XI Adapter: RFC:
If the RFC adapter is used with SNC, the name and location of the SNC library installed on the system must be provided to the RFC layer. You can do this in various ways and with the following order of precedence:
? Set the Path to SNC library parameter in the configuration of the RFC sender channel in the Integration Directory (SNC advanced mode).
? Set the pathToSNCLibraryDefault service property of the RFC adapter.
? Set a platform-specific parameter (for example, the process environment). For more information about this option, see the SNC documentation for the relevant platform.