- Windows server 2008 R2/MSSQL server 2012
- NetWeaver 7.3 EHP 1 Java
- Kernel – 721 Patch 200
- CPS 8.0 – M33.104
- Target DB – MSSQL server 2012
- ProcessServerService.JDBC.limit license key
- Domain\SAPServiceSID user should have access to the target Database server and database.
- Make sure the jdbc 4 driver file sqljdbc4.jar are located in F:\usr\sap\SID\J00\exe\mssjdbc\jdbc4
- Download and place the sqljdbc_auth.dll file for JDBC 4 version from Microsoft and place in C:\Windows\System32
the version of dll file should be the same as the JDBC driver:
- Upload the jdbc 4 driver to CPS from Libraries located under Scripting on the left side navigation pane.
Provide a name for the library, it should always start with “Custom_”
In JAR Files tab, click the upload button and upload the jar file from the location specified in the prerequisite.
- Create a new process server of type JDBC, and select the MSSQL server option and select the JDBC driver 4 we just uploaded in step 1.
In the following screen provide the database server information and use the string “integratedSecurity=True” in options field.
We still have to provide the userid/password to save the credential, even though the password will not be used to connect or run the jobs.
It will take to the next screen to validate the information. The process server is now created successfully.
- JVM crash
In our Sandbox environment, when we used JDBC 4 version,the JVM crashed on completion of Step 2 mentioned above, forcing the Primary Application Server (Server 0) to reboot. Process server got created successfully when we used JDBC version 3.
In our development environment, the JVM crashed when we used JDBC version 3, and worked fine with JDBC version 4.
Both environment had same os version, kernel version, SP stack level, same DB version.
With the guidance of Redwood support we identified that even though the Java kernel was same, the JDBC 4 drivers between the two environments had different check sums.
So we copied overwrote the JDBC driver 4 file from DEV to SBX, and that fixed the issue.
It is also important to pay attention to the sqljdbc_auth.dll file’s version, it should be the same as the JDBC driver version.