SAP Adapter connection is not getting enabled and it does not show any error message

The WmSAP Adapter connection from IS to S4 HANA is not getting enabled and also it is not showing any error message.

The same set of connection parameters are being used by SAP MII system and they are able to connect where as from IS it does not connect and also does not show any error or success message.

We have followed the SAP adapter configuration steps and copied the respective jars to the folders and restarted the IS and the the server classpath is shown as below.

E:\SoftwareAG\IntegrationServer\instances\Instance2_LocalDev\packages\WmSAP\code\jars\static\sapidoc3.jar
E:\SoftwareAG\IntegrationServer\instances\Instance2_LocalDev\packages\WmSAP\code\jars\static\sapjco3.jar
E:\SoftwareAG\IntegrationServer\instances\Instance2_LocalDev\packages\WmSAP\code\jars\static\wmsap.jar

WmSAP adapter is also seen as the output of the list of registered adapters.

The IS/OS details are as below

OS.Name Windows Server 2012
OS.Release 6.2 OS.Build.no. 9200
CPU.cores 4

Software
Product webMethods Integration Server
Version 10.1.0.0
Updates IS_10.1_Core_Fix1

Build Number 99

Please let us know as the connection is not getting enabled nor it is showing any message when you try to enable the connection.

One thing that was noticed was that when the IS is restarted the WmSAP adapter is loaded fully. When you reload the WmSAP adapter package it gets partially loaded and shows the message as below.

wm.sap.Admin:registerAdapter WmSAP Adapter: Error on creating new Object: ServerDataProvider already registered [com.wm.adapter.sap.SAPAdapterManager]
wm.sap.Admin:registerRoutingListener WmSAP Adapter: Error on creating new Object: [ART.115.3209] Adapter Runtime (Listener): Error creating listener object wm.sap.internal.ls:routingListener. Error: java.lang.NullPointerException. null

please let us know if this is a cause for the issue.

Regards,
Suneetha

Hi Suneetha,

please provide the fix version applied to SAP Adapter as well as the version of the JCo api.
Latest Fix for SAP Adapter I am aware of is SAP_7.1_Fix18 and latest JCo version should be 3.0.18, for JCoIDoc the latest version is 3.0.12.
The version info can be found on the about page of SAP Adapter Admin UI.

Remember that JCo as a native part (a dll for windows or a so-lib for *nix derivates).
This should be located under E:\SoftwareAG\IntegrationServer\instances\Instance2_LocalDev\lib.

Due to the nature of having a native library part SAP Adapter cannot be reloaded online, but requires a complete restart of the IS.

Regards,
Holger

Hi Holger,
Thanks for your response. The sap adapter version and the JCo versions are listed as below from the SAP Adapter page.

We are using the IS trial (Version 10.1.0.0 ) in our dev server, so please let us know if that could have any impact on the adapter configurations.

We do not have the SAP adapter fix you mentioned applied currently. We are facing issues downloading it from the site. please let us know if it is mandatory to apply this fix or if there any alternate way to get this fix. the update manager is not working properly and this fix is available for download via the update manager.

Description webMethods SAP Adapter
Adapter Version 7.1.0.0.718
Updates None
JCA Spec Version 1.0
Vendor Name Software AG

OS Version 6.3
Current User svc.WMD-VCENPRPCD010
Working Directory E:\SoftwareAG\IntegrationServer\instances\Instance2_LocalDev

JCo Version 3.0.12 (2014-11-21)
JCo Middleware JavaRfc
JCo Middleware Version 2.2.13
JCo Native Library Version 720.713
JCo Native Library Location E:\SoftwareAG\IntegrationServer\instances\Instance2_LocalDev\lib\jars\sapjco3.dll
IDoc Library Version 3.0.11 (2014-06-20)

Regards,
Suneetha

Hi Suneetha,

as there were some internal changes to the JCo libs which were causing issues with the SAP Adapter you should apply latest fix for SAP Adapter.

Please note that WAR_10.1_Fix2 is required for SAP_7.1_Fix18.
This WAR_10.1_Fix2 is a fix for the AdapterRuntime (ART) and can be found in the IntgrationServer group in UpdateManager.

Can you describe what is going wrong while using UpdateManager?

Regards,
Holger

Hi Holger,
The update manager is not getting launched and we tried to reinstall it but that seems to be not happening either. It throws some error mentioned below. As we are using trial version of WM we will not be able to download the fixes. So I think we need to wait till we get the licensed WM.

Please suggest if there is any other alternate approach or any other aspect that can be analyzed and pursued further to fix this issue.

Thank you for your support so far.

31.05.2018 16:01:56 INFO | ------------------------- SoftwareAG Update Manager Launcher ------------------------ |
31.05.2018 16:01:56 FINEST ENTER SUMLogger > setupLockStructure()
31.05.2018 16:01:56 FINEST | Check if another process is started already
31.05.2018 16:01:56 FINEST | There is no other processes started from this installation
31.05.2018 16:01:56 FINEST | Trying to create new ‘.lock’ file
31.05.2018 16:01:56 FINEST | ‘.lock’ file is created successfully
31.05.2018 16:01:56 FINEST | Check if ‘exit_code.txt’ file exists
31.05.2018 16:01:56 FINEST | ‘exit_code.txt’ doesn’t exist
31.05.2018 16:01:56 FINEST EXIT SUMLogger < setupLockStructure()
31.05.2018 16:01:56 INFO | Software AG Update Manager home directory: C:\SAGUpdateManager1
31.05.2018 16:01:56 INFO | You can find the log files in C:\SAGUpdateManager1\logs\launcher.log
31.05.2018 16:01:56 INFO |
31.05.2018 16:01:56 FINEST ENTER StepContext > defineTypeOfProcess()
31.05.2018 16:01:56 FINEST | Config properties file: C:\SAGUpdateManager1\bin\config.properties is not existing → this is a new installation
31.05.2018 16:01:56 INFO | This is a new Software AG Update Manager installation
31.05.2018 16:01:56 INFO |
31.05.2018 16:01:56 FINEST EXIT StepContext < defineTypeOfProcess()
31.05.2018 16:01:56 FINEST ENTER StepContext > defineServer()
31.05.2018 16:01:56 FINEST | HTTP connection will be used [port 80]
31.05.2018 16:01:56 FINEST | The ‘-sumServer’ is initialized with default value: sdc.softwareag.com:80
31.05.2018 16:01:56 FINEST EXIT StepContext < defineServer()
31.05.2018 16:01:56 FINEST ENTER StepContext > imageOperation()
31.05.2018 16:01:56 FINEST | Checks if ‘-createImage’ is needed to perform: false
31.05.2018 16:01:56 FINEST EXIT StepContext < imageOperation()
31.05.2018 16:01:56 FINEST ENTER StepContext > imageOperation()
31.05.2018 16:01:56 FINEST | Checks if ‘-createImageOnly’ is needed to perform: false
31.05.2018 16:01:56 FINEST EXIT StepContext < imageOperation()
31.05.2018 16:01:56 FINEST ENTER StepContext > imageOperation()
31.05.2018 16:01:56 FINEST | Checks if ‘-installFromImage’ is needed to perform: true
31.05.2018 16:01:56 FINEST EXIT StepContext < imageOperation()
31.05.2018 16:01:56 FINEST ENTER StepContext > imageOperation()
31.05.2018 16:01:56 FINEST | Checks if ‘-createSourceDir’ is needed to perform: false
31.05.2018 16:01:56 FINEST EXIT StepContext < imageOperation()
31.05.2018 16:01:56 FINEST ENTER StepContext > imageOperation()
31.05.2018 16:01:56 FINEST | Checks if ‘-installFromSourceDir’ is needed to perform: false
31.05.2018 16:01:56 FINEST EXIT StepContext < imageOperation()
31.05.2018 16:01:56 FINEST ENTER StepContext > defineMode()
31.05.2018 16:01:56 FINEST | SUM application will be started in gui mode
31.05.2018 16:01:56 FINEST EXIT StepContext < defineMode()
31.05.2018 16:01:56 FINEST ENTER StepContext > setCredentials()
31.05.2018 16:01:56 FINEST | Setting credentials
31.05.2018 16:01:56 FINEST EXIT StepContext < setCredentials()
31.05.2018 16:01:56 FINEST ENTER StepManager > executeSteps()
31.05.2018 16:01:56 INFO | ================= CURRENT COMPONENT VERSIONS - START ======================
31.05.2018 16:01:56 INFO | There is no existing config.properties file C:\SAGUpdateManager1\bin\config.properties
31.05.2018 16:01:56 INFO | ================= END CURRENT COMPONENT VERSIONS - START ==================
31.05.2018 16:01:56 INFO |
31.05.2018 16:01:57 FINEST SKIP DeleteTempsSeparately
31.05.2018 16:01:57 FINEST SKIP SetProxyConfFromFile
31.05.2018 16:01:57 FINEST SKIP CheckSUMServer
31.05.2018 16:01:57 FINEST SKIP ExitWithNoUpdate
31.05.2018 16:01:57 FINEST SKIP ConnectToTheSUMServer
31.05.2018 16:01:57 FINEST SKIP GetVersionsFromRepoByInstall
31.05.2018 16:01:57 FINEST ENTER CreateTempDirByInstallation > run()
31.05.2018 16:01:57 FINEST | The tmp directory is: C:\SAGUpdateManager1\tmp
31.05.2018 16:01:57 FINEST EXIT CreateTempDirByInstallation < run()
31.05.2018 16:01:57 FINEST SKIP DownloadSUMComponentsFromServer
31.05.2018 16:01:57 FINEST SKIP DownloadSUMComponentsFromRepo
31.05.2018 16:01:57 FINEST ENTER GetVersionsFromImageByInstall > run()
31.05.2018 16:01:57 FINEST | The tmp directory is: C:\SAGUpdateManager1\tmp
31.05.2018 16:01:57 INFO | Installing SUM from image file
31.05.2018 16:01:57 FINEST | Verifying that the given image file U:\webMethods10.1-all\wm101_fix_img.zip is valid
31.05.2018 16:01:57 FINEST | Searching for ‘components’ directory
31.05.2018 16:01:57 FINEST | The given image contains ‘components’ directory
31.05.2018 16:01:57 FINEST | Searching for ‘response.json’ file
31.05.2018 16:01:57 FINEST | The given image contains ‘response.json’ file
31.05.2018 16:01:57 FINEST | Searching for ‘launcher.zip’ file
31.05.2018 16:01:57 FINEST | The given image contains ‘launcher.zip’ file
31.05.2018 16:01:57 FINEST | Searching for ‘sum.zip’ file
31.05.2018 16:01:57 FINEST | The given image contains ‘sum.zip’ file
31.05.2018 16:01:57 FINEST | Searching for ‘jvm.zip’ file
31.05.2018 16:01:57 FINEST | The given image contains ‘jvm.zip’ file
31.05.2018 16:01:57 FINEST | Searching for ‘osgi.zip’ file
31.05.2018 16:01:57 FINEST | The given image contains ‘osgi.zip’ file
31.05.2018 16:02:05 FINEST | File with components versions from image: C:\SAGUpdateManager1\tmp\components\response.json
31.05.2018 16:02:05 FINEST | File with components versions loaded successfully
31.05.2018 16:02:05 FINEST EXIT GetVersionsFromImageByInstall < run()
31.05.2018 16:02:05 FINEST SKIP GetVersionsFromSourceByInstall
31.05.2018 16:02:05 FINEST ENTER VerifyImagePlatform > run()
31.05.2018 16:02:05 FINEST EXIT VerifyImagePlatform < run()
31.05.2018 16:02:05 FINEST ENTER UnzipSUMComponentsFromImage > run()
31.05.2018 16:02:05 FINEST | The tmp directory is: C:\SAGUpdateManager1\tmp
31.05.2018 16:02:29 SEVERE o-------------------LAUNCHER_ERROR-------------------o
31.05.2018 16:02:29 SEVERE o Message: Unexpected end of ZLIB input stream
31.05.2018 16:02:29 SEVERE o Exception: java.io.EOFException
31.05.2018 16:02:29 SEVERE o Stacktrace:
31.05.2018 16:02:29 SEVERE o java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:240)
31.05.2018 16:02:29 SEVERE o java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
31.05.2018 16:02:29 SEVERE o java.util.zip.ZipInputStream.read(ZipInputStream.java:194)
31.05.2018 16:02:29 SEVERE o java.io.FilterInputStream.read(FilterInputStream.java:107)
31.05.2018 16:02:29 SEVERE o com.softwareag.plm.sum.client.launcher.utils.ZipTool.readFromZip(ZipTool.java:67)
31.05.2018 16:02:29 SEVERE o com.softwareag.plm.sum.client.launcher.utils.ZipTool.unZipIt(ZipTool.java:115)
31.05.2018 16:02:29 SEVERE o com.softwareag.plm.sum.client.launcher.steps.impl.UnzipSUMComponentsFromImage.unzipAll(UnzipSUMComponentsFromImage.java:54)
31.05.2018 16:02:29 SEVERE o com.softwareag.plm.sum.client.launcher.steps.impl.UnzipSUMComponentsFromImage.run(UnzipSUMComponentsFromImage.java:88)
31.05.2018 16:02:29 SEVERE o com.softwareag.plm.sum.client.launcher.steps.AbstractAction.begin(AbstractAction.java:76)
31.05.2018 16:02:29 SEVERE o com.softwareag.plm.sum.client.launcher.steps.StepManager.executeSteps(StepManager.java:58)
31.05.2018 16:02:29 SEVERE o com.softwareag.plm.sum.client.launcher.Launcher.main(Launcher.java:51)
31.05.2018 16:02:29 SEVERE o----------------------------------------------------o
31.05.2018 16:02:29 FINEST EXIT UnzipSUMComponentsFromImage < run()
31.05.2018 16:02:29 FINEST | Exit from check() method
31.05.2018 16:02:29 FINEST | The code in the ‘exit_code.txt’ is: 179 Error in unzipping of a zip file
31.05.2018 16:02:29 FINEST | Trying to delete ‘.lock’ file: \bin.lock
31.05.2018 16:02:29 FINEST | Delete successfull
31.05.2018 16:02:29 SEVERE o====================================================o
31.05.2018 16:02:29 SEVERE Exit code: 179 Error in unzipping of a zip file
31.05.2018 16:02:29 INFO |
31.05.2018 16:02:29 INFO | Exit from Launcher: 179
31.05.2018 16:02:29 INFO |

Regards,
Suneetha

Hi Suneetha,

looks like there is a damaged Fix-File in the image.

You should try to download a new Fix-Image.

Regards,
Hiolger

Hi Holger,
We have tried to apply the latest patches using Update Manager but the SAP adapter fix seems not to have got updated. please let us know as this issue is still not fixed. And when we try to enable the sap adapter connection it does not show any message success or failure. please suggest. Thank you

the SAP adapter about page looks as follows.

About SAP Adapter
Copyright

Copyright © 1996-2009 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or their suppliers.
All rights reserved.

The name Software AG, webMethods and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc.
Other company and product names mentioned herein may be trademarks of their respective owners.

Description webMethods SAP Adapter
Adapter Version 7.1.0.0.718
Updates None
JCA Spec Version 1.0
Vendor Name Software AG

OS Version 6.3
Current User svc.WMD-VCENPRPCD010
Working Directory E:\SoftwareAG\IntegrationServer\instances\default

JCo Version 3.0.18 (2018-03-23)
JCo Middleware JavaRfc
JCo Middleware Version 2.2.22
JCo Native Library Version 721.1016
JCo Native Library Location E:\SoftwareAG\IntegrationServer\instances\default\lib\sapjco3.dll
IDoc Library Version 3.0.12 (2015-02-10)

Regards,
Suneetha

Hi Suneetha,

which tree did you check in UpdateManager for the Fixes?

SAP Adapter Fix should be located under “7.1.0 → Adapters”.

After the Fix was applied the About-Page should contain these informations.
Adapter Version 7.1.0.18.914
Updates SAP_7.1_Fix18
JCA Spec Version 1.0
Vendor Name Software AG

Regards,
Holger

Hi Holger,
Thanks for your response. The fix is applied now and the about page of SAP adapter shows as below.

But the adapter connection is not getting enabled. When we click on the Enable Yes/No link in the connection it asks for confirmation in a pop up box whether to enable or not. But nothing happens after that. there are no logs as well.

Please help us to fix this issue. Thank you.

About SAP Adapter
Copyright

Copyright © 2016 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.

The name Software AG and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA Inc. and/or its subsidiaries and/or its affiliates and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners.

Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located at http://softwareag.com/licenses.

Use of this software is subject to adherence to Software AG’s licensing conditions and terms. These terms are part of the product documentation, located at http://softwareag.com/licenses and/or in the root installation directory of the licensed product(s).

This software may include portions of third-party products. For third-party copyright notices, license terms, additional rights or restrictions, please refer to “License Texts, Copyright Notices and Disclaimers of Third Party Products”. For certain specific third-party license restrictions, please refer to section E of the Legal Notices available under “License Terms and Conditions for Use of Software AG Products / Copyright and Trademark Notices of Software AG Products”. These documents are part of the product documentation, located at http://softwareag.com/licenses and/or in the root installation directory of the licensed product(s).

Description webMethods SAP Adapter
Adapter Version 7.1.0.18.914
Updates SAP_7.1_Fix18

JCA Spec Version 1.0
Vendor Name Software AG

OS Version 6.3
Current User svc.WMD-VCENPRPCD010
Working Directory E:\SoftwareAG\IntegrationServer\instances\default

JCo Version 3.0.18 (2018-03-23)
JCo Middleware JavaRfc
JCo Middleware Version 2.2.22
JCo Native Library Version 721.1016
JCo Native Library Location E:\SoftwareAG\IntegrationServer\instances\default\lib\sapjco3.dll
IDoc Library Version 3.0.12 (2015-02-10)

Hi Suneetha,

did you rememeber to apply WAR_10.1_Fix2 to your IS installation as this one is required by SAP_7.1_Fix18 for IS 10.1?

Is there anything in the server.log during startup which might be related to the SAP Adapter package?

Please check the Logging configuration for IS Server.log and SAP Adapter.
The Log factory for the WmSAP package in Server Logger should be set to “10-Trace”, usually SAP Adapter sets this automatically if it is not set. You can then configure the Logging in the SAP Adapter Logging section inside the SAP Adapter.

Did you configure the C:\Windows\system32\drivers\etc\services configuration to include the required SAP Ports?
For the Dispatchers these are 3200 thru 3299 and for the gateways these are 3300 thru 3399.
See SAP Adapter Installation Guide and SAP Adapter Readme for further informations regarding this.

Can you share a sample of your connection config, please?

Regards,
Holger

Hi Holger,
We installed an older version i.e. WAR_10.1_Fix1. I installed the latest version WAR_10.1_Fix2 and the issue is fixed now. I could see the logs after increasing the adapter log level. All other suggested configuration settings were in place.

Thank you so much for all your support.

Regards,
Suneetha