+

Search Tips   |   Advanced Search

Automating administrative architecture setup library

The scripting library provides Jython script procedures to assist in automating the environment. Use the server, node, and cluster management scripts to configure servers, nodes, node groups, and clusters in the application server environment.

Before we can complete this task, install an application server in the environment.

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.

Use the scripts in the following directories to configure the administrative architecture:

Each script from the directory automatically loads when you launch wsadmin.sh. To automatically load our own Jython scripts (*.py) when wsadmin.sh starts, set the wsadmin.script.libraries system property to the script location.

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

Use the following steps to create a node group and add three nodes to the group:

  1. Optional: Launch wsadmin.sh.

    Use this step to launch wsadmin.sh and connect to a server, job manager, or administrative agent profile, or run the tool in local mode. If we launch wsadmin.sh, use the interactive mode examples to run scripts.

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

        wsadmin -lang jython

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

        wsadmin -conntype none -lang jython

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

  2. Display the nodes in the environment.

    Run the listNodes script procedure from the AdminNodeManagement script library:

      bin>wsadmin -lang jython -c "AdminNodeManagement.listNodes()"

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

      wsadmin>AdminNodeManagement.listNodes()

    For this example, the command returns the following output:

    Node1
    Node2
    Node3

  3. Create a node group.

    Run the createNodeGroup script procedure from the AdminNodeGroupManagement script library, specifying the name to assign to the new node group:

      bin>wsadmin -lang jython -c "AdminNodeGroupManagement.createNodeGroup("NodeGroup1")"

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

      wsadmin>AdminNodeGroupManagement.createNodeGroup("myNodeGroup")

  4. Add nodes to the node group.

    Run the addNodeGroupMember script procedure from the AdminNodeGroupManagement script library to add the Node1, Node2, and Node3 nodes to the NodeGroup1 node group, specifying the node name and node group name, as the following examples demonstrate:

    wsadmin -lang jython -c "AdminNodeGroupManagement.addNodeGroupMember("Node1", "NodeGroup1")"
    wsadmin -lang jython -c "AdminNodeGroupManagement.addNodeGroupMember("Node2", "NodeGroup1")"
    wsadmin -lang jython -c "AdminNodeGroupManagement.addNodeGroupMember("Node3", "NodeGroup1")"

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

    wsadmin>AdminNodeGroupManagement.addNodeGroupMember("Node1", "NodeGroup1")
    wsadmin>AdminNodeGroupManagement.addNodeGroupMember("Node2", "NodeGroup1")
    wsadmin>AdminNodeGroupManagement.addNodeGroupMember("Node3", "NodeGroup1")


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:


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 the app_server_root/scriptLibraries directory.


Subtopics


Related tasks

  • Use the script library to automate the application serving environment

  • Server configuration scripts