!--a11y-->
Configure the JCO Client Service 
The JCO client service can be configured in EP5.0 with the service.xml file. All time values in the service.xml file are specified in milliseconds. The service has the following properties:
This property specifies the size of the pool table. The pool table stores all pools. The size should be approximately the number of Portal users accessing a R/3 system with the JCO client service. The table is automatically extended when needed. Extending the table is time consuming, so the initial value should not be to small.
The PoolSizeDefault property defines the default pool size for all destinations. If the property PoolSize is not specified for a destination, the default pool size value is used.
The property PoolSize can be used to specify a pool size for a individual destination. All pools containing JCO clients to a destination have the same size. Values for the PoolSize property are separated by semicolons.
This property limits the destinations per user. The limit is equal to the pool size. Values are separated by semicolons.
This property defines the time span the JCO client service tries to provide a pool entry before a TimeoutException is thrown.
The property AvailableClientTimeoutDefault specifies the time a JCO client can reside in a pool before the JCO client service removes it. This time can be overwritten for every destination using the property AvailableClientTimeout. Values for property AvailableClientTimeout are separated by semicolons.
This internal property is relevant for the performance of the JCO client service and should be approximately PoolTableInitialSize/3.
Specifies the repositories to clear. Multiple repositories have to be separated by semicolons.
The interval by which the repositories are cleared. If tis property is not provided, the repositories are cleared only once. The minimum value is 300000 milliseconds (5 minutes).
Property in web.xml file of the EP 5.0:
This value is specified in file:
webapps\irj\WEB-INF\web.xml
Section:
<session-timeout>30</session-timeout>
Value is specified in minutes.
The entries in the service.xml file look as follows:
PoolTableInitialSize = "100"
PoolSizeDefault = "8"
PoolSize = "
LimitPerUserForDestination = "
WaitForConnectionTimeout = "3000"
AvailableClientTimeoutDefault = "300000"
AvailableClientTimeout = "
NumberOfTimers = "3"
Settings to define the pool size for R/3 destination PLM to 6 and SAP_FIN as 10:
PoolSize = "PLM=6;SAP_FIN=10"
Settings to limit the connections for SAP_FIN to 10:
PoolSize = "PLM=6;SAP_FIN=10"
LimitPerUserForDestination = "SAP_FIN"
Settings to set the timeout for JCO clients in the pool belonging to PLM to 2 minutes and for SAP_FIN to 6 minutes:
AvailableClientTimeout = "PLM=120000;SAP_FIN=360000"
For pool monitoring the JCOClientPoolLogger in file logger.xml has to be switched on.
A log entry is created every time a JCO client is requested (when the getJCOClientPoolEntry() method is called). The pool state is written to the log file:
...\webapps\irj\WEB-INF\plugins\portal\logs\JCOClientPool.log
