This example demonstrates how you can add a MySQL connector for the vRealize Orchestrator SQL plug-in.

Prerequisites

The vRealize Orchestrator SQL plug-in supports only certain database database types. Before adding a MySQL connector, verify that your are using one of the following database types:

  • Oracle
  • Microsoft SQL Server
  • PostgreSQL
  • MySQL

Procedure

  1. Add the MySQL connector.jar file to the vRealize Orchestrator Appliance.
    1. Log in to the vRealize Orchestrator Appliance command line over SSH as root.
    2. Navigate to the /data/vco/var/run/vco directory. 
      cd /data/vco/var/run/vco
    3. Create a plugins/SQL/lib/ directory. 
      mkdir -p plugins/SQL/lib/
    4. Copy your MySQL connector.jar file from your local machine to the /data/vco/var/run/vco/plugins/SQL/lib/ directory by running a secure copy (SCP) command. 
      scp ~/local_machine_dir/your_mysql_connector.jar root@orchestrator_FQDN_or_IP:/data/vco/var/run/vco/plugins/SQL/lib/
      Note: You can also use alternative methods for copying your connector.jar file to the vRealize Orchestrator Appliance, such as PSCP.
  2. Add the new MySQL property to the Control Center.
    1. Log in to the Control Center as root.
    2. Select System Properties.
    3. Click New.
    4. Under Key, enter o11n.plugin.SQL.classpath.
    5. Under Value, enter /var/run/vco/plugins/SQL/lib/your_mysql_connector.jar.
      Note: The value text box can include multiple JDBC connectors. Each JDBC connector is separated by a semicolon (";"). For example: 
      /var/run/vco/plugins/SQL/lib/your_mysql_connector.jar;/var/run/vco/plugins/SQL/lib/your_mssql_connector.jar;/var/run/vco/plugins/SQL/lib/your_other_connector.jar
    6. (Optional) Enter a description for the MySQL system property.
    7. Click Add, and wait for the vRealize Orchestrator server to restart.
      Note: Do not save your JDBC connector.jar file in another directory and do not set a different value to the o11n.plugin.SQL.classpath property. Otherwise, the JDBC connector becomes unavailable to your vRealize Orchestrator deployment.