Using application properties files to install, update, and delete enterprise application files

You can use application properties files to install enterprise application files on a server, update deployed applications or modules, or uninstall deployed applications or modules. An enterprise application file must conform to Java Platform, Enterprise Edition (Java EE) specifications.

Before you begin

Before you can install enterprise application files on an application server, you must assemble modules as needed. Also, configure the target application server. As part of configuring the server, determine whether your application files can be installed to your deployment targets.

Start the wsadmin scripting tool. To start wsadmin using the Jython language, run the wsadmin -lang Jython command from the bin directory of the deployment target profile.

About this task

Using an application properties file, you can install, update, or uninstall an enterprise application or module.

Run administrative commands using wsadmin to deploy an application.

Table 1. Actions for application properties files. You can specify properties that install, update, or uninstall applications.
Action Procedure
create (install) 1. Specify properties that identify the application and deployment target.

2. Run the applyConfigProperties command to install the application.

modify (update) 1. Edit application properties in the properties file. To update an application file, specify in the Properties section:
  • Update=true
  • operationType=add, operationType=update or operationType=delete
  • contentType=file, contentType=moduleFile, contentType=partialapp, or contentType=app

2. Run the applyConfigProperties command to update the deployed application.

delete (uninstall) 1. Remove properties that identify the deployment target from the properties file.

2. Run the deleteConfigProperties command to uninstall the deployed application.

create Property Not applicable
delete Property Not applicable

Optionally, you can use interactive mode with the commands:

AdminTask.command_name('-interactive')

Instead of running the wsadmin commands manually to apply an application properties file, you can add the properties file to a monitored directory. The product automatically runs the wsadmin commands. See Installing enterprise application files by adding properties files to a monitored directory.

If you are installing a stand-alone web application archive (WAR) or a Session Initiation Protocol (SIP) archive (SAR), specify the context root of the WAR or SAR file. 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.

This topic describes how to complete the following procedures:

Procedure

Results

You can use the properties file to configure and manage the application object and its properties.

What to do next

Save the changes to your configuration.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 4:16:02 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-dist&topic=txml_config_prop_app
File name: txml_config_prop_app.html