Pattern matching using the wsadmin scripting tool

Use the Jython or Jacl scripting language to implement pattern matching when installing, updating, or editing an application. Pattern matching simplifies the task of supplying required values for certain complex options by allowing you to pass in asterisk (*) to all of the required values that cannot be edited.

Before you begin

There are two ways to complete this task. This topic uses the AdminApp object to install enterprise applications. Alternatively, you can use the scripts in the AdminApplication script library to install, uninstall, and administer your application configurations with many options, including pattern matching.

The scripting library provides a set of procedures to automate the most common administration functions. You can run each script procedure individually, or combine several procedures to quickly develop new scripts.

Procedure

  • Install each web application archive (WAR) and Java™ archive file to the application server.
    1. Start the wsadmin scripting tool.
    2. Install each web application archive (WAR) and Java archive file to the application server, as the following examples demonstrate:
      • Using Jython:
        AdminApp.install('DefaultApplication.ear', ['-appname', 'TEST', '-MapModulesToServers', [['.*', 
         '.*', 'WebSphere:cell=myCell,node=myNode,server=myServer']]])
      • Using Jacl:
        $AdminApp install DefaultApplication.ear {-appname TEST -MapModulesToServers
          {{.* .* WebSphere:cell=myCell,node=myNode,server=myServer}}}
    3. Save your configuration changes.
      Use the following command example to save your configuration changes:
      AdminConfig.save()
  • Install each WAR file to the myServer server on the myNode node and each JAR file to the yourServer server on the yourNode node.
    1. Start the wsadmin scripting tool.
    2. Install the WAR and JAR files to different application server management scopes, as the following examples demonstrate:
      • Using Jython:
        AdminApp.install('DefaultApplication.ear', ['-appname', 'TEST', '-MapModulesToServers', [['.*', 
         '.*.war,.*', 'WebSphere:cell=myCell,node=myNode,server=myServer'], ['.*', '.*.jar,.*', 
         'WebSphere:cell=myCell,node=yourNode,server=yourServer']]])
      • Using Jacl:
        $AdminApp install DefaultApplication.ear {-appname TEST -MapModulesToServers 
          {{.* .*.war,.* WebSphere:cell=myCell,node=myNode,server=myServer} 
          {.* .*.jar,.* WebSphere:cell=myCell,node=yourNode,server=yourServer}}}
    3. Save your configuration changes.
      Use the following command example to save your configuration changes:
      AdminConfig.save()