Network Deployment (Distributed operating systems), v8.0 > Scripting 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 application configuration properties files
Work with application configuration EJB module properties files
We can use properties files to create, modify, or delete EJB module configuration objects of an application configuration. An EJB module must conform to Java EE specifications.
Determine the changes to make to an EJB module configuration of an application configuration.
Start wsadmin.sh.
To start wsadmin using the Jython language, run...
WP_PROFILE/bin/wsadmin -lang jython
Use a properties file, you can create, modify, or delete an EJB module.
Run administrative commands using wsadmin to create or change a properties file for an EJB module, validate the properties, and apply them to the configuration.
Actions for application configuration EJB module configuration properties files. We can create, modify, and delete EJB module configuration properties.
Action Procedure create Set required properties and then run applyConfigProperties. modify Make required changes to properties and then run applyConfigProperties. delete To delete the entire ApplicationConfig EJBModuleConfig object, uncomment #DELETE=true and then run deleteConfigProperties. create Property Not applicable delete Property Not applicable Optionally, you can use interactive mode with the commands:
AdminTask.command_name('-interactive')
Procedure
- Create a properties file for an ApplicationConfig EJBModuleConfig object.
- Set ApplicationConfig EJBModuleConfig properties as needed.
Open an editor on an ApplicationConfig EJBModuleConfig properties file. Modify the Environment Variables section to match the system and set any property value that needs to be changed. An example ApplicationConfig EJBModuleConfig properties file follows:
# # Header (ApplicationConfig EJBModuleConfig) # ResourceType=EJBModuleConfig ImplementingResourceType=Application ResourceId=Cell=!{cellName}:Deployment=!{applicationName}:ApplicationDeployment=:ApplicationConfig=: EJBModuleConfig =myEJBModule #DELETE=true # # #Properties # name=myEJBModule description=null # EnvironmentVariablesSection # # #Environment Variables cellName=myCell04 applicationName=myApp- Run applyConfigProperties to create or change an EJB module.
Run applyConfigProperties 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 '])
- Modify an existing properties file.
- Obtain a properties file for the EJB module configuration to change.
We can extract a properties file for an ApplicationConfig EJBModuleConfig object using the extractConfigProperties command.
- Open the properties file in an editor and change the properties as needed.
Ensure that the environment variables in the properties file match the system.
- Run applyConfigProperties.
- If you no longer need the EJB module configuration, you can delete the entire EJB module configuration object.
To delete the entire object, specify DELETE=true in the header section of the properties file and run deleteConfigProperties; for example:
AdminTask.deleteConfigProperties('[-propertiesFileName myObjectType.props -reportFileName report.txt]')
Results
We can use the properties file to configure and manage the EJB module configuration and its properties.
What to do next
Save the changes to the configuration.
Extract 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
Related
PropertiesBasedConfiguration command group using wsadmin.sh