Frequent changes of SAP PI java properties in below cases
XPI Adapter: XI
You may need to change the following properties of the service XPI 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 24 hours.
If you expect a message load that exceeds the maximum database size within 24 hours, you must reduce this value before the first messages are sent, because changes to this value will only affect new messages.
XPI Service: Messaging System
You may need to change the following properties of the service XPI Service: Messaging System :
The headers of synchronous messages are kept in main storage for monitoring purposes. Therefore, the main storage available to AS Java 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
This property determines how often the headers of synchronous (error-free) messages are to be removed from main storage.
You can modify this property by using the SAP NetWeaver Administrator.
The Adapter Engine messaging system delivers messages to enterprise Java beans (EJBs) and tries to read these EJBs from the JNDI when starting the Messaging System service.
This property determines how often and at what time intervals the messaging service tries to find the EJBs.
Since EJBs are part of Java applications and therefore only started after the Java 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 AS Java, 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.
XPI Service: CPA Cache
You may need to change the following properties of the service XPI Service: CPA 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.
XPI Adapter: RFC
You may need to change the following property of the service XPI 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, refer to the SNC documentation for the relevant platform.
XPI Service: AF Core
You may need to change the following property of the service XPI Service: AF Core :
The Adapter Engine is able to send and receive messages in parallel by using respective send or receive queues for each adapter type. The name of the adapter type (and of the corresponding queue) is retrieved from the CPA cache, for example RFC_http://sap.com/xi/XI/System .
The default values for the number of poll attempts, the poll interval, and the sending and receiving consumer threads are set by the global property set as follows:
(name=global, messageListener=localejbs/AFWListener, exceptionListener= localejbs/AFWListener,, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=5, Rqst.maxConsumers=5)
To set individual values for a specific adapter type, you have to add a new property set to the default set with the name of the respective adapter type, for example:
(name=RFC_http://sap.com/xi/XI/System, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=7, Recv.maxConsumers=7, Call.maxConsumers=7, Rqst.maxConsumers=7)