How to deploy third party libs for JCS custom connector on Vaap

book

Article ID: 224697

calendar_today

Updated On:

Products

CA Identity Manager

Issue/Introduction

Custom connectors that uses third party libraries for encryption and other data manipulation.
On Standalone deployment it was deployed the jars in JCS_HOME\lib\ext but on VAPP have NO permissions on that folder.
How should deploy those jar files?

Environment

Release : 14.3

Component :

Resolution

1) Install the connector server on a separate system, connect it to your VApp and then you can copy and paste the jar files in the lib/ext folder on the external connector server. In VApp there are permission restrictions. So this option is most likely the easier route to perform but requires another machine.

2) Create an OSGI bundle.  https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-3/programming/connector-programming-reference/packaging-and-deploying-a-connector/how-to-migrate-a-connector-to-osgi/.html

The documentation mention that you can use Bundle Builder to convert an existing connector.jar file to an OSGi bundle. This makes the connector hot-deployable.