WAS v8.5 > Script the application serving environment (wsadmin) > Use properties files to manage system configuration > Manage specific configuration objects using properties files > Use application properties files to install, update, and delete enterprise application files > Work with application deployment properties files

Work with web module deployment properties files

We can use properties files to modify web module deployment properties. A web module must conform to Java EE specifications.

Determine the changes to make to the web module deployment configuration.

Start the wsadmin scripting tool. To start wsadmin using the Jython language, run the wsadmin -lang Jython command from the bin directory of the server profile. Using a properties file, we can modify a web module deployment object.

Run administrative commands using wsadmin to change a properties file for a web module deployment, validate the properties, and apply them to your configuration.

Actions for web module deployment properties files. We can modify web module deployment properties.

Action Procedure
create Not applicable
modify Edit the properties file and then run the applyConfigProperties command.
delete Not applicable
create Property Not applicable
delete Property Not applicable

Optionally, we can use interactive mode with the commands:

  1. Edit a web module deployment configuration.

    For example, specify properties such as the following for a WebModuleDeployment instance:

    #
    # Header
    #
    ResourceType=WebModuleDeployment
    ImplementingResourceType=Application
    ResourceId=Cell=!{cellName}:Deployment=!{applicationName}:ApplicationDeployment=:WebModuleDeployment=
    uri#myWebModule.war
    #
    
    #
    #Properties
    #
    startingWeight=10000 #integer,required,default(1)
    deploymentId=1 #required
    classloaderMode=PARENT_FIRST #ENUM(PARENT_FIRST|PARENT_LAST),default(PARENT_FIRST)altDD=null
    uri=myWebModule.war #required
    applicationDeployment=Cell=!{cellName}:Deployment=!{applicationName2}:ApplicationDeployment=ID#
    ApplicationDeployment_1183122148265 #ObjectName(ApplicationDeployment)
    
    #
    # Header ( WebDeployment ClassLoader)
    #
    ResourceType=Classloader
    ImplementingResourceType=Application
    ResourceId=Cell=!{cellName}:Deployment=!{applicationName}:ApplicationDeployment=:WebModuleDeployment=uri
    #myWebModule.war:Classloader=
    #
    
    #
    #Properties
    #
    mode=PARENT_FIRST #ENUM(PARENT_FIRST|PARENT_LAST),default(PARENT_FIRST)
    
    
    #
    # Header ( WebDeployment ClassLoader's LibraryRef )
    #
    ResourceType=LibraryRef
    ImplementingResourceType=Application
    ResourceId=Cell=!{cellName}:Deployment=!{applicationName}:ApplicationDeployment=:WebModuleDeployment=uri
    #myWebModule.war:Classloader=:LibraryRef=libraryName#myLibName
    #
    
    #
    #Properties
    #
    libraryName=myLibName 
    sharedClassLoader=null
    
    #
    EnvironmentVariablesSection
    #
    #
    #Environment Variables
    cellName=myCell04
    applicationName=myApp

  2. Run the applyConfigProperties command to change a web module deployment configuration.

    Running the applyConfigProperties command applies the properties file to the configuration. In this Jython example, the optional -reportFileName parameter produces a report named report.txt:

      AdminTask.applyConfigProperties(['-propertiesFileName myObjectType.props -reportFileName report.txt '])


Results

We can use the properties file to manage the web module deployment object and its properties.

Save the changes to your configuration.


Related


Extracting properties files using wsadmin.sh
Create server, cluster, application, or authorization group objects using properties files and wsadmin scripting
Delete server, cluster, application, or authorization group objects using properties files


Reference:

PropertiesBasedConfiguration command group for AdminTask using wsadmin.sh


+

Search Tips   |   Advanced Search