Application installation and uninstallation scripts

The scripting library provides multiple script procedures to automate your application configurations. See the usage information for scripts that install applications. You can run each script individually or combine procedures to create custom automation scripts for your environment.

[Windows]The file path specified for the earFile argument can use forward (/) or backward (\) slashes. For example, both c:\ears\MyApp.ear and c:/ears/MyApp.ear are supported values for earFile.

installAppWithDefaultBindingOption

This script installs an application using the -usedefaultbindings option.

To run the script, specify the application name, enterprise archive (EAR) file, data source Java™ Naming and Directory Interface (JNDI) name, data source user name, data source password, connection factory, Enterprise JavaBeans prefix, and virtual host name arguments, as defined in the following table:
Table 1. installAppWithDefaultBindingOption argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the target node.
serverName Specifies the name of the target server.
dsJndiName Specifies the JNDI name of the data source to use.
dsUserName Specifies the user name for the data source.
dsPassword Specifies the password for the data source.
connFactory Specifies the name of the connection factory to use.
EJBprefix Specifies the Enterprise JavaBeans (EJB) prefix to use.
virtualHostName Specifies the virtual host for the application to install.

Syntax

AdminApplication.installAppWithDefaultBindingOption(appName, earFile,
 nodeName, serverName, dsJndiName, dsUserName,
 dsPassword, connFactory, EJBprefix, virtualHostName)

Example usage

[Windows]
AdminApplication.installAppWithDefaultBindingOption("myApp", "c:/ears/DefaultApplication.ear",
 "myNode", "myServer", "myJndi", "user1", "password", "myCf", "myEjb", "myVH")
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppWithDefaultBindingOption("myApp", "/ears/DefaultApplication.ear",
 "myNode", "myServer", "myJndi", "user1", "password", "myCf", "myEjb", "myVH")

installAppWithNodeAndServerOptions

This script installs an application using the -node and -server options.

To run the script, specify the application name, EAR file, node name, and server name arguments, as defined in the following table:
Table 2. installAppWithNodeAndServerOptions argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName Specifies the name of the application server of interest.

Syntax

AdminApplication.installAppWithNodeAndServerOptions(appName, earFile,
 nodeName, serverName)

Example usage

[Windows]
AdminApplication.installAppWithNodeAndServerOptions("myApp", "c:/ears/DefaultApplication.ear",
 "myNode", "myServer") 
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppWithNodeAndServerOptions("myApp", "/ears/DefaultApplication.ear",
 "myNode", "myServer") 

installAppWithClusterOption

This script installs an application using the -cluster option.

To run the script, specify the application name, EAR file, and cluster name arguments, as defined in the following table:
Table 3. installAppWithClusterOption argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
clusterName Specifies the name of the cluster of interest.

Syntax

AdminApplication.installAppWithClusterOption(appName, earFile, clusterName)

Example usage

[Windows]
AdminApplication.installAppWithClusterOption("myApp", "c:/ears/DefaultApplication.ear", "myCluster") 
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppWithClusterOption("myApp", "/ears/DefaultApplication.ear", "myCluster") 

installAppModulesToSameServerWithMapModulesToServersOption

This script deploys application modules to the same server using the -MapModulesToServers option.

To run the script, specify the application name, EAR file, node name, and server name arguments, as defined in the following table:
Table 4. installAppModulesToSameServerWithMapModulesToServersOption argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName Specifies the name of the application server of interest.

Syntax

AdminApplication.installAppModulesToSameServerWithMapModulesToServersOption(appName, 
 earFile, nodeName, serverName)

Example usage

[Windows]
AdminApplication.installAppModulesToSameServerWithMapModulesToServersOption("myApp", 
 "c:/ears/DefaultApplication.ear", "myNode", "myServer")
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppModulesToSameServerWithMapModulesToServersOption("myApp", 
 "/ears/DefaultApplication.ear", "myNode", "myServer")

installAppModulesToDiffServersWithMapModulesToServersOption

This script deploys application modules to different servers using the -MapModulesToServers option. Use this script to install application modules to one or two servers. To install to additional servers, create a custom script based on the syntax in the AdminApplication.py file, or run the script multiple times.

To run the script, specify the application name, EAR file, node name, and both server name arguments, as defined in the following table:
Table 5. installAppModulesToDiffServersWithMapModulesToServersOption argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName1 Specifies the name of the application server to which the application is deployed.
serverName2 Specifies the name of an additional application server to which the application is deployed.

Syntax

AdminApplication.installAppModulesToDiffServersWithMapModulesToServersOption(appName, 
 earFile, nodeName, serverName1, serverName2)

Example usage

[Windows]
AdminApplication.installAppModulesToDiffServersWithMapModulesToServersOption("myApp", 
 "c:/ears/DefaultApplication.ear", "myCell", "myNode", "myServer1", "myServer2") 
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppModulesToDiffServersWithMapModulesToServersOption("myApp", 
 "/ears/DefaultApplication.ear", "myCell", "myNode", "myServer1", "myServer2") 

installAppModulesToSameServerWithPatternMatching

This script deploys application modules with the -MapModulesToServers pattern matching option.

To run the script, specify the application name, EAR file, node name, and server name arguments, as defined in the following table:
Table 6. installAppModulesToSameServerWithPatternMatching argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName Specifies the name of the application server of interest.

Syntax

AdminApplication.installAppModulesToSameServerWithPatternMatching(appName, 
 earFile, nodeName, serverName)

Example usage

[Windows]
AdminApplication.installAppModulesToSameServerUingPatternMatching("myApp",
 "c:\ears\DefaultApplication.ear", "myNode", "myServer") 
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppModulesToSameServerUingPatternMatching("myApp", 
 "/ears/DefaultApplication.ear", "myNode", "myServer") 

installAppModulesToDiffServersWithPatternMatching

This script deploys application modules to different servers using the -MapModulesToServers pattern matching option. Use this script to install application modules to one or two servers. To install to additional servers, create a custom script based on the syntax in the AdminApplication.py file, or run the script multiple times.

To run the script, specify the application name, EAR file, node name, and both server name arguments, as defined in the following table:
Table 7. installAppModulesToDiffServersWithPatternMatching argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName1 Specifies the name of the application server to which the application is deployed.
serverName2 Specifies the name of an additional application server to which the application is deployed.

Syntax

AdminApplication.installAppModulesToDiffServersWithPatternMatching(appName, 
 earFile, nodeName, serverName1, serverName2)

Example usage

[Windows]
AdminApplication.installAppModulesToDiffServersWithPatternMatching("myApp", 
 "c:\ears\DefaultApplication.ear", "myNode", "myServer1", "myServer2")
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppModulesToDiffServersWithPatternMatching("myApp",
 "/ears/DefaultApplication.ear", "myNode", "myServer1", "myServer2")

installAppModulesToMultiServersWithPatternMatching

This script deploys application modules to multiple servers using the -MapModulesToServers pattern matching option. Use this script to install application modules to one or two servers. To install to additional servers, create a custom script based on the syntax in the AdminApplication.py file, or run the script multiple times.

To run the script, specify the application name, EAR file, node name, and each server name arguments, as defined in the following table:
Table 8. installAppModulesToMultiServersWithPatternMatching argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName1 Specifies the name of the application server to which the application is deployed.
serverName2 Specifies the name of an additional application server to which the application is deployed.

Syntax

AdminApplication.installAppModulesToMultiServersWithPatternMatching(appName, 
 earFile, nodeName, serverName1, serverName2)

Example usage

[Windows]
AdminApplication.installAppModulesToMultiServersWithPatternMatching("myApp", 
 "c:\ears\DefaultApplication.ear", "myCell", "myNode", "myServer1", "myServer2")
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppModulesToMultiServersWithPatternMatching("myApp", 
 "/ears/DefaultApplication.ear", "myCell", "myNode", "myServer1", "myServer2")

installAppWithTargetOption

This script deploys an application to multiple servers using the -target option. Use this script to install application modules to one or two servers. To install to additional servers, create a custom script based on the syntax in the AdminApplication.py file, or run the script multiple times.

To run the script, specify the application name, EAR file, node name, and each server name arguments, as defined in the following table:
Table 9. installAppWithTargetOption argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName1 Specifies the name of the application server to which the application is deployed.
serverName2 Specifies the name of an additional application server to which the application is deployed.

Syntax

AdminApplication.installAppWithTargetOption(appName, earFile, nodeName,
 serverName1, serverName2)

Example usage

[Windows]
AdminApplication.installAppWithTargetOption("myApp", "c:\ears\DefaultApplication.ear", "myNode",
 "myServer1", "myServer2")
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppWithTargetOption("myApp", "/ears/DefaultApplication.ear", "myNode",
 "myServer1", "myServer2")

installAppWithDeployEjbOptions

This script deploys an application with the -deployejb option.

To run the script, specify the application name and EAR file arguments, as defined in the following table:
Table 10. installAppWithDeployEjbOptions argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.
nodeName Specifies the name of the target node.
serverName Specifies the name of the target server.

Syntax

AdminApplication.installAppWithDeployEjbOptions(appName, earFile,
 nodeName, serverName)

Example usage

[Windows]
AdminApplication.installAppWithDeployEjbOptions("myApp", "c:\ears\DefultApplication.ear",
 "myNode", "myServer")
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppWithDeployEjbOptions("myApp", "/ears/DefultApplication.ear",
 "myNode", "myServer")

installAppWithVariousTasksAndNonTasksOptions

This script deploys an application with various tasks and non-tasks options.

To run the script, specify the application name and EAR file arguments, as defined in the following table:
Table 11. installAppWithVariousTasksAndNonTasksOptions argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
earFile Specifies the EAR file to deploy.

Syntax

AdminApplication.installAppWithVariousTasksAndNonTasksOptions(appName, earFile)

Example usage

[Windows]
AdminApplication.installAppWithVariousTasksAndNonTasksOptions("myApp", "c:\ears\DefaultApplication.ear")
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installAppWithVariousTasksAndNonTasksOptions("myApp", "/ears/DefaultApplication.ear")

installWarFile

This script installs a web application archive (WAR) file. A web module is created by assembling servlets, JavaServer Pages (JSP) files, and static content such as Hypertext Markup Language (HTML) pages into a single deployable unit. Web modules are stored in web application archive (WAR) files, which are standard Java archive files.

To run the script, specify the application name, WAR file, node name, server name, and context root arguments, as defined in the following table:
Table 12. installWarFile argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to install.
warFile Specifies the WAR file to deploy.
nodeName Specifies the name of the node of interest.
serverName Specifies the name of the application server of interest.
contextRoot Specifies the context root of the web application. The context root is combined with the defined servlet mapping (from the WAR file) to compose the full URL that users type to access the servlet. For example, if the context root is /gettingstarted and the servlet mapping is MySession, then the URL is http://host:port/gettingstarted/MySession.

Syntax

AdminApplication.installWarFile(appName, warFile,
 nodeName, serverName, contextRoot)

Example usage

[Windows]
AdminApplication.installWarFile("myApp", "c:\binaries\DefaultWebApplication.war",
 "myNode", "myServer", "/") 
[Linux][AIX][z/OS][HP-UX][IBM i][Solaris]
AdminApplication.installWarFile("myApp", "/binaries/DefaultWebApplication.war",
 "myNode", "myServer", "/")

uninstallApplication

This script uninstalls an application.

To run the script, specify the application name argument, as defined in the following table:
Table 13. uninstallApplication argument descriptions . Run the script with argument values.
Argument Description
appName Specifies the name of the application to uninstall.

Syntax

AdminApplication.uninstallApplication(appName)

Example usage

AdminApplication.uninstallApplication("myApp")