We need to connect to a Maria DB via AFX. For that we need to add the Driver for Maria DB:
But neither the connector template for generic DB nor for MySQL allow to add custom files
Where we need to add the driver?
I think you might also face other issues trying to do so since there isn't a MariaDB connector template. Also the GenericDB connector template only allows you to select from a list of predefined connectors/classes.
What you could try is to place that jar file under <AFX_Path>/esb/lib/user/ or <AFX_Path>/esb/lib/opt/ (but not both), Restart AFX and try again. However this is completely experimental and most likely not supported.
So we don't have any guide or instructions to install MariaDB connector in the application?
Is there a way to add the MariaDB to the Generic DB template?
I think that is answered already.
As noted in this discussion a customer was referred to KB 000029641 for guidance for a similar driver.
It has been reported that this did not work.
We do not have any way to install arbitrary drivers or jars for custom connectors.
There are precedents for adding similar jars for the generic database driver and we do provide guidance as to where best to install the library jars. I assume you could do a similar thing for your custom connector.
000033869 - Questions on creating an AFX connector to PostgreSQL using a generic ODBC driver in RSA Identity Governance & Lifecycle
Be aware that patching and updating AFX will overwrite these changes.
I am having a customer who wants to deploy custom AFX connector to MariaDB. Their environment is Websphere and remote DB, version 7.1.0.Does anyone have any idea what are the steps to deploy the mariadb-java-client-2.4.4.jar with AFX?
1.Acording to KB https://community.rsa.com/docs/DOC-81196 , I recommended the customer to follow the steps and move the jar file to /AFX/esb/lib/user then install it but it didn't work.2. Also I recommended to follow this article https://community.rsa.com/docs/DOC-94146 but they don't have ACMcustomize.sh script as they're using Webshpere, so I gave them the generic steps as below after referring to their Admin but they want specified steps adapted to their environment:> unwrap the ear file then the contents of the currently deployed aveksa.ear will be extracted to a directory "x" for example>Move the jar fie and wrap it to the directory x/aveksa.war/WEB-INF/LocalAgent/common/lib to add the driver to the application library.>Go to the .ear file directory to:-Change the file's user and group owners to orace:oinstall-Change the file permissions to rw- for both owner and group owner>Then Rebuild the .ear file after modifying it.
Connectors and Collectors are deployed in completely different applications, Connectors in the AFX Tomcat application and Collectors in the main WebSphere aveksa application ear.
customizeACM.sh cannot be used for connectors. It cannot be used on Websphere.
Retrieving data ...