How to setup JCO Connection Pooling in SMP 3.0
This technical document explains how to setup JCO connection pooling in SUP/SMP. JCO is the driver used to connect to SAP back end Data Servers. We will explore the available configuration options for connection pooling and what is supported and what versions of SMP that are needed to be used.
DESCRIPTION Connection pooling can speed up the connection process. By setting the refresh and time to live for the connection in the pool help keep the connection up to date. This does not improve data processing only the connection and log in processing to the back end server.
- SMP 3.0 or higher.
- JCO connection to a SAP R3 Backend..
- This document assumes you have a working SMP environment.
- You have an SAP R3 CRM, ERP Backend
- Have Administrator rights to the Operating System and Sybase Unwired Server.
- You have configured a JCO connection thru SCC to connect to SAP.
- Need to implement Connection Pooling.
- In SMP/SUP no option for connection pooling.
- In SCC for JCO there are no Connection pooling.
Under SUP/SMP Connection pooling for the JCO is not available as an option this is by design. There is JVM memory and performance consideration that need to be taken in to consideration when implementing JCO connection pooling. Adding in JCO destination pooling properties into a SUP server SAP connection is an UNKNOWN/UNQUANTIFIED risk as to any memory loading the SAP JCO sub systems may add to the Virtual memory footprint of the server OS. You must test for best results in you environment.
Step 1 Creating a JCO connection properties file:
- Use a text editor like Notepad and create a connection.properties file in C:\temp\ connection.properties
- Add the following to your connection.properties file. # BASE SUP properties
# Type of remote host 2 = R/2, 3 = R/3, E = External
#jco.client.type=”3″ We will default to 3 so no need to use this line.
#Pool properites from the JCo v3
#Maximum number of active connections that #can be created for a destination simultaneously
#Maximum number of idle connections kept open by the destination. #A value of 0 has the effect that there is no connection pooling.
#Time in ms after that the connections hold by the destination can be closed
#Period in ms after that the destination checks the released connections for expiration
#Max time in ms to wait for a connection, if the max allowed number #of connections is #allocated by the application jco.destination.max_get_client_time=30000
- Edit the connection.properties and add the server and domain address you will also need to add the correct user and password information as well check and make sure you have all the correct information to connect to the SUP server.
- Save the file.
Now that we have created our connection properties we will need to import the file into the SUP Workspace.
Step 2 Importing the JCO connection properties file in to SUP.
- Start the SUP Workspace from the desktop icon.
2. Go to Enterprise Explorer then tree open SAP Servers
Right Click on SAP Servers Folder and select New
3. Change the Name: To something like SAP Pooling TEST.
- Click Next >.
5. At the very top we now need to select Create from Properties file.
. Click the Brows Button
Brows to the Temp directory where we created the connection.properties file
- Select the connection.properties file and click on Open.
- Then Click on Next.
- After Click Next we should see the following Screen.
GUI. You have to edit the connection properties file. If the information looks correct Click Finish.
Now that we have completed the creation of our JCO connection that will use connection pool we need to open the connection and test it.
Step 3: Testing the newly created connection with pooling.
Go to the Enterprise Explorer and tree open the SAP Server folder.
You should now see the SAP Pooling Test.
1- Right Click the data source SAP Pooling Test and select Connect.
You should now be connected to your SAP server
This concludes the steps needed to create a JCO connection profile that enables the JCO connection pooling in SIP/SMP Workplace.
Issue2 After deploying the MBO’s with Connection pooling enable the data values are not migrated over to SUP.
When deploying to the SMP server the data values for the Connection pooling is not there they are stripped when sent to SUP Server.
This is by design in order to add the connection pooling option in SCC you have to edit the JCO connection and use the pull down menu
This is current only supported with SMP versions 2.2.4 or higher. In the older versions of SUP there is no interface option to add a user defined option for the drivers. to add the option you will need to add a user defined properties add the property value jco.destination.peak_limit and then add the data value 50 you will need to do this for each connection pooling option
1- Select a connection property from the menu see Figure 9
2- Highlight and back space to remove the reference.
3- Add jco.destination.peak_limit
4- Click on the menu item to add you Data value 50
5- Repeat each steps until you have all 4 values entered
6- When done do a test connect
7- Save and exit.
This document explained in details how to setup JCO Connection pooling in SUP/SMP. As you can see the steps are very easy and can help to improve the connection processes. As with any changes you should test before fully implementing the changes and make any adjustment if needed. Connection pooling can in most environments will improve the connection processes to the back end servers. A big Thanks goes out to Lance Waterman and Duncan Rigby from SUP engineering in assisting in figuring this all out.