JCo connection broke after deployment

[Former Member]

At this moment we do not have setup the JDI environment (we are busy with it). When we do a deploy of Java WD with EAR files through SDM or we do it via NWDS our JCo connection is broken every time.

Initially we have set the JCo connections to 'ticket' but after we make changes to a WD and deploy it via SDM or NWDS the JCo connection is set back to UID/PW. Does anybody have any idea why this happens?

Kind regards,

Dave Arends

[former_member85655 · Accepted solution]

Hi Dave,

The configuration for JCO as JCO destinations is done on the content administrator and is independent of the application itself. So I dont understand deploying the application interferes with JCO.

Regards,

Arun

[Former Member · Accepted solution]

That's the problem we are facing with. We also don't understand why JCo connections get broken after deployment of the WD