Automate application configurations using the scripting library


 

+

Search Tips   |   Advanced Search

 

The scripting library provides Jython script procedures to assist in automating the environment. Use the application management scripts to install, uninstall, export, start, stop, and manage applications in the environment.

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

The application management procedures in scripting library are located in...

WAS_HOME/scriptLibraries/application/V70

Each script from the directory automatically loads when you launch wsadmin. To automatically load the own Jython scripts (*.py) when wsadmin starts, create a new subdirectory and save existing automation scripts under...

WAS_HOME/scriptLibraries

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

Use the AdminApplication.py scripts to perform multiple combinations of administration functions.

Use the following steps to use the scripting library to install an application on a cluster and start the application:

  1. Launch wsadmin.

    Use this step to launch wsadmin and connect to a server, or run the tool in local mode. If we 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 Jython:

      bin>wsadmin -conntype none -lang jython

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

  2. Create a cluster.

    Run the createClusterWithoutMember script procedure from the AdminClusterManagement script library, and specify the required arguments...

    bin>wsadmin -lang jython -c "AdminClusterManagement.createClusterWithoutMember('myCluster')"

    We can also use interactive mode to run the script procedure...

    wsadmin>AdminClusterManagement.createClusterWithoutMember("myCluster")

  3. Create a cluster member for the new cluster.

    Run the createClusterMember script procedure from the AdminClusterManagement script library, and specify the required arguments...

    bin>wsadmin -lang jython -c "AdminClusterManagement.createClusterMember('myCluster', 'myNode, 'myNewMember')"

    We can also use interactive mode to run the script procedure...

    wsadmin>AdminClusterManagement.createClusterWithoutMember("myCluster", "myNode", "myNewMember")

  4. Install the application on the newly created cluster.

    Run the installAppWithClusterOption script procedure from the AdminApplication script library, and specify the required arguments...

    bin>wsadmin -lang jython -c "AdminApplication.installAppWithClusterOption('myApplication','myApplicationEar.ear','myCluster')"

    We can also use interactive mode to run the script procedure...

    wsadmin>AdminApplication.installAppWithClusterOption("myApplication", "myApplicationEar.ear", "myCluster")

  5. Start the application on the cluster.

    Run the startApplicationOnCluster script procedure from the AdminApplication script library and specify the required arguments...

    bin>wsadmin -lang jython -c "AdminApplication.startApplicationOnCluster('myApplication','myCluster')"

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

    wsadmin>AdminApplication.startApplicationOnCluster("myApplication", "myCluster")

 

Results

The wsadmin script libraries return the same output as the associated wsadmin commands. For example, the script...

AdminServerManagement.listServers()

...returns a list of available servers.

The script...

AdminClusterManagement.checkIfClusterExists()

...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:

wsadmin>AdminApplication.startApplicationOnCluster("myApplication","myCluster","true")

 

What to do next

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

WAS_HOME/scriptLibraries


Application installation and uninstallation scripts
Application query scripts
Application update scripts
Application export scripts
Application deployment configuration scripts
Application administration scripts

 

Related tasks

Use the script library to automate the application serving environment