UCSD - How to load a SQL jar file via Script Module Example

Version 2
    Task Name

    Example on how to load a SQL jar file into UCSD via script Module.

    Description

     

    Prerequisites

    Tested on UCSD 6.0.0.0

    CategoryWorkflow
    ComponentsvSphere 5.x
    User Inputs


    Instructions for Regular Workflow Use:

    1. Download the attached .ZIP file below to your computer. *Remember the location of the saved file on your computer.
    2. Unzip the file on your computer. Should end up with a .WFD file.
    3. Log in to UCS Director as a user that has "system-admin" privileges.
    4. Navigate to "Policies-->Orchestration" and click on "Import".
    5. Click "Browse" and navigate to the location on your computer where the .WFD file resides. Choose the .WFD file and click "Open".
    6. Click "Upload" and then "OK" once the file upload is completed. Then click "Next".
    7. Click the "Select" button next to "Import Workflows". Click the "Check All" button to check all checkboxes and then the "Select" button.
    8. Click "Submit".
    9. A new folder should appear in "Policies-->Orchestration" that contains the imported workflow. You will now need to update the included tasks with information about the specific environment.

     

    A thank you goes out to Paul Kunzler for the inspiration:

     

     

    Fine the SQL jar file on Microsofts web site. I found it here: https://msdn.microsoft.com/en-us/library/ms378526(v=sql.110).aspx

     

    Down load the SQL jar file and extract it:

     

    Screen Shot 2017-01-10 at 8.10.19 AM.png

     

    Screen Shot 2017-01-10 at 8.11.29 AM.png

     

    Create a script module SQL42:

     

    Screen Shot 2017-01-10 at 8.12.03 AM.png

     

    Screen Shot 2017-01-10 at 8.12.15 AM.png

     

    Upload the jar file to UCSD:

     

    Screen Shot 2017-01-10 at 8.12.34 AM.png

     

    Screen Shot 2017-01-10 at 8.12.54 AM.png

     

    The upload result and path:

     

    Screen Shot 2017-01-10 at 8.13.24 AM.png

     

    Create a custom task:

     

    Screen Shot 2017-01-10 at 8.14.07 AM.png

     

    Screen Shot 2017-01-10 at 8.15.20 AM.png

     

    ASCII version (PATH may differ in your install !!!!):

     

    loadJar("SQL42/sqljdbc42.jar");

    importClass(com.microsoft.sqlserver.jdbc.SQLServerDataSource);

    var ds = new Packages.com.microsoft.sqlserver.jdbc.SQLServerDataSource();

     

     

    Create workflow using this new task:

     

    Screen Shot 2017-01-10 at 8.27.36 AM.png

     

    Run the workflow:

     

    Screen Shot 2017-01-10 at 8.18.37 AM.png

     

    Screen Shot 2017-01-10 at 8.18.52 AM.png

     

    Export of the workflow does contain the script module and the SQL jar file:

     

    Screen Shot 2017-01-10 at 8.19.22 AM.png