DAMLink SAP Commerce Cloud Integration connection issue

Rohan Shinde · 2023-06-30T20:58:47+00:00

There was an error rendering this rich post.

We are currently using "SAP Hybris Digital Asset Management 22.1.0 by OpenText" and working on migrating from v22.1 to v22.4 (required to support Hybris v2211).

We are facing connectivity issues with the OTMM APIs. We understand that OTMM internally uses Jersey client for the API endpoint connectivity and the current SAP Hybris OTMM extensions (v22.1) that we have connect to the API endpoints fine.

API endpoint - https://<hostname>/otmmapi/v5/sessions/

The connectivity to this endpoint fails with HTTP 503 error with the new SAP Hybris OTMM extensions (v22.4). When we debugged the issue, we found that the new extensions use JDK Connector (org.glassfish.jersey.jdk.connector.JdkConnectorProvider) to initiate the API call as opposed to HttpUrlConnectorProvider (org.glassfish.jersey.client.HttpUrlConnectorProvider), that is used by the previous version.

When connecting with HttpUrlConnectorProvider we see that it works fine but with JdkConnectorProvider it fails. Is there any setting/configuration that we need to enable for the APIs to work with v22.4. We checked the upgrade documentation and couldn't find anything specific to this.

Find more posts tagged with

Comments

Rohan Shinde

We are using SSO to connect to the APIs -

otmm.server.sso = true

Jeremy Naylor

Not sure if this is related, but there are some patches that should be applied that may impact what you are experiencing. Specifically KB0785962 touches on some authentication issues. I'd verify those are applied.

Rohan Shinde

Thanks for your response Jeremy ! Is this KBA a SAP KB number or OpenText article number? Asking because, no results are displayed when I search for it KB0785962.

Jeremy Naylor

It will be under Patches and not necessarily KBA's

https://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0785962

See if that link works for you

Rohan Shinde

Thanks, I am able to access the link, but the search displays no result for that KBA number. Also, I tried searching for patches/articles that contains the authentication change that you mentioned but couldn't find any. Please could share a direct link to it or a screenshot. Sorry for the trouble !

Jeremy Naylor

Hmm I have a feeling this might be an issue with your account, What I'd suggest is creating a support ticket and direct it to the KC team to figure out the permissions.

It includes a binary that needs to be applied, which I can't provide a direct link for unfortunately.

Rohan Shinde

Thanks, I will work on updating my access. In the mean time, just wanted to share the installable/patches that we have used for OTMM. Please could you confirm if the files look correct and if the binary that you mentioned is already part of these packages -

We have used the following OTMM extensions installable zip file –

damlink-commerce-integration-22.4.0.zip

and here are the patches we have installed on top of it –

damlink_commerce-220400-001.zip (specifically damlink-smartedit-commerce2211-22.4.0-Build22.4.0.1.zip inside the parent zip)
damlink_commerce-220400-002.zip

Jeremy Naylor

Yup that looks right, but part of this is also dependent on what patch level on the commerce cloud side. So for instance, there is an issue currently that smartedit doesn't work with certain patch levels on the commerce cloud side. I believe, we have an issue with right now we only support 2211.5 , 2211.8 is due to be supported in 23.3 of the damlink integration.

That might be what you are encountering? As the patches you've mentioned are essentially the patches I was referring to with my link above. So that's a moot point.

If those options don't pan out, I'd suggest creating a support ticket and we can review this. If its in North america, likely will be me that you will work with.

Rohan Shinde

Thanks Jeremy, we initially tried the OTMM extensions mentioned above with 2211.8 as that's the commerce patch version we are planning to upgrade to. We noticed a build issue with 2211.8, so just for testing the new OTMM extensions, we went back to 2211.0 (patch 0, base version).

The original issue mentioned on this thread is the issue we are facing with 2211.0.

We have also created a SAP ticket and is currently assigned to an OTMM support person, I am not sure which location he is from.

Jeremy Naylor

I'll take a look for it, likely APAC or EU region then.