cancel
Showing results for 
Search instead for 
Did you mean: 

CC 5.2 JCo connectors not visible in CC

Former Member
0 Kudos

We have installed Compliance Calibrator 5.2 on our NW04S system, which already had Access Enforcer 5.2 installed. We have created and successfuly tested our JCo connectors in NW. Our SLD connector is tested successfully.

When we try to create a connector from within CC, we get nothing in the drop-down for JCO Destination. If we try to search for a connector name in AE, we get nothing.

We have verified that our CC user account is OK in SAP, and has the CC Administrator role in SAP.

We have verified that the SLD account is not expired or locked.

Any help will be appreciated.

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This sounds like an issue with your SLD defintion. The second step in the creation of the JCo (J2EE Cluster), what option are using? Are you using a local SLD or a global SLD?

Former Member
0 Kudos

Hi, Michael,

We are using a global SLD. We are able to create the connectors from the NW box, and they show up in the SLD. We have the SLD connector (with user and password) configured, and tested successfully. Next we are going to test using the JCo connectors mentioned in OSS note 1009267. Which connectors have you used?

Thanks!

Former Member
0 Kudos

Jennifer,

Can you let us know which JCo destinations you used for Meta Data and Model Data.

Regards,

Muthu Kumaran KG

Former Member
0 Kudos

Hi, Muthu!

We first tried VIRSAXSR3_01_MODEL and METADATA, since we do not have an HR system. Next we tried the same names..."02" and they did not work either. Have you had any luck with those?

Thanks.

Jennifer

Former Member
0 Kudos

Jennifer,

I would suggest you try this also.,

VIRSAR3_01_MODEL

VIRSAR3_01_METADATA

And I believe you have defined your SLD data supplier in the SLD.

Thanks.

Regards,

Muthu Kumaran KG

Answers (1)

Answers (1)

Former Member
0 Kudos

Switching to those connectors worked. Thanks!