WAS v8.5 > Script the application serving environment (wsadmin) > Use the script library to automate the application serving environment using wsadmin.sh

Automating data access resource configuration using wsadmin.sh

The scripting library provides Jython script procedures to assist in automating the environment. Use the resource management scripts to manage your Java Database Connectivity (JDBC) configurations.

The scripting library provides a set of procedures to automate the most common application server administration functions. There are three ways to use the Jython script library.

The data access resource management procedures in the scripting library are located in the app_server_root/scriptLibraries/resources/JDBC/V70 subdirectory. Each script from the directory automatically loads when we launch wsadmin. To automatically load our own Jython scripts (*.py) when wsadmin starts, save your automation scripts to a new subdirectory in the app_server_root/scriptLibraries directory.

Best practice: To create custom scripts using the scripting library procedures, save the modified scripts to a new subdirectory to avoid overwriting the library. Do not edit the script procedures in the scripting library.

We can use the scripts to perform many combinations of administration functions. Use the following sample combination of procedures to configure a JDBC provider and data source.

  1. Verify that all of the necessary JDBC driver files are installed on your node manager. If you opt to configure a user-defined JDBC provider, check the database documentation for information about the driver files.

  2. Optional: Launch wsadmin.

    Use this step to launch wsadmin and connect to a server, or run the tool in local mode. If you launch wsadmin, use the interactive mode examples in this topic to run scripts.

    • Enter the following command from the bin directory to launch wsadmin and connect to a server:

        bin>wsadmin -lang jython

    • Enter the following command from the bin directory to launch wsadmin in local mode and using the Jython scripting language:

        bin>wsadmin -conntype none -lang jython

    When wsadmin launches, the system loads all scripts from the scripting library.

  3. Configure a JDBC provider.

    Run the createJDBCProvider procedure from the script library and specify the required arguments. To run the script, specify the node name, server name, name to assign to the new JDBC provider, and the implementation class name. We can optionally specify additional attributes in the following format: [["attr1", "value1"], ["attr2", "value2"]]. Custom properties for specific vendor JDBC drivers must be set on the application server data source. Consult the database documentation for information about available custom properties.

    The following example creates a JDBC provider in your configuration:

    bin>wsadmin -lang jython -c "AdminJDBC.createJDBCProvider("myNode", "myServer", "myJDBCProvider",
     "myImplementationClass", [["description", "testing"], ["xa", "false"], ["providerType", "provType"]])"

    We can also use interactive mode to run the script procedure, as the following example displays:

    wsadmin>AdminJDBC.createJDBCProvider("myNode", "myServer", "myJDBCProvider", "myImplementationClass",
     [["description", "testing"], ["xa", "false"], ["providerType", "provType"]])

    The script returns the configuration ID of the new JDBC provider.

  4. Use a template to configure a data source.

    Run the createDataSourceUsingTemplate procedure from the script library and specify the required arguments. To run the script, specify the node name, server name, JDBC provider name, configuration ID of the template to use, and the name to assign to the new data source. We can optionally specify additional attributes in the following format: [["attr1", "value1"], ["attr2", "value2"]].

    The following example uses a template to create a data source in your configuration:

    bin>wsadmin -lang jython -c "AdminJDBC.createDataSourceUsingTemplate("myNode", "myServer", "myJDBCProvider",
     "Derby JDBC Driver DataSource(templates/system|jdbc-resource-provider-templates.xml#DataSource_derby_1)",
     "myDataSource", [["authDataAlias", "myalias"], ["authMechanismPreference", "BASIC_PASSWORD"],
     ["description", "testing"], ["jndiName", "dsjndi1"], ["logMissingTransactionContext", "true"],
     ["statementCacheSize", "5"]])"

    We can also use interactive mode to run the script procedure, as the following example displays:

    wsadmin>AdminJDBC.createDataSourceUsingTemplate("myNode", "myServer", "myJDBCProvider", "Derby JDBC Driver 
     DataSource(templates/system|jdbc-resource-provider-templates.xml#DataSource_derby_1)", "myDataSource", 
     [["authDataAlias", "myalias"], ["authMechanismPreference", "BASIC_PASSWORD"], ["description", "testing"],
     ["jndiName", "dsjndi1"], ["logMissingTransactionContext", "true"], ["statementCacheSize", "5"]])

    The script returns the configuration ID of the new data source.


Results

The wsadmin script libraries return the same output as the associated wsadmin commands. For example, the AdminServerManagement.listServers() script returns a list of available servers. The AdminClusterManagement.checkIfClusterExists() script returns a value of true if the cluster exists, or false if the cluster does not exist. If the command does not return the expected output, the script libraries return a 1 value when the script successfully runs. If the script fails, the script libraries return a -1 value and an error message with the exception.

By default, the system disables failonerror option. To enable this option, specify true as the last argument for the script procedure, as the following example displays:

Create custom scripts to automate the environment by combining script procedures from the scripting library. Save custom scripts to a new subdirectory of the app_server_root/scriptLibraries directory.


Subtopics


Related


Configure a JDBC provider and data source
Use the script library to automate the application serving environment using wsadmin.sh


Reference:

Data source minimum required settings, by vendor


+

Search Tips   |   Advanced Search