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 application configuration properties files > Work with application configuration EJB module properties files

Work with EJB module configuration session manager properties files

We can use properties files to create, modify, or delete session manager objects of an EJB module configuration. An EJB module must conform to Java EE specifications.

Determine the changes to make to a session manager of an EJB module 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 create, modify, or delete a session manager.

Run administrative commands using wsadmin to create or change a properties file for a session manager, validate the properties, and apply them to your configuration.

Actions for EJB module configuration session manager properties files. We can create, modify, and delete session manager properties.

Action	Procedure
create	Set required properties and then run the applyConfigProperties command.
modify	Make required changes to properties and then run the applyConfigProperties command.
delete	To delete the entire EJBModuleConfig SessionManager object, uncomment #DELETE=true and then run the deleteConfigProperties command.
create Property	Not applicable
delete Property	Not applicable

Optionally, we can use interactive mode with the commands:

AdminTask.command_name('-interactive')

• Create a properties file for an EJBModuleConfig SessionManager object.

  1. Set EJBModuleConfig SessionManager properties as needed.

     Open an editor on an EJBModuleConfig SessionManager properties file. Modify the Environment Variables section to match the system and set any property value that needs to be changed. To specify a custom property, edit the AttributeInfo value and properties values. An example EJBModuleConfig SessionManager properties file follows:

     #
     # Header (EJBModuleConfig Session Manager)
     #
     ResourceType=SessionManager
     ImplementingResourceType=Application
     ResourceId=Cell=!{cellName}:Deployment=!{applicationName}:ApplicationDeployment=:ApplicationConfig=:EJBModuleConfig=myEJBModule:SessionManager=
     AttributeInfo=sessionManagement
     #DELETE=true
     #
     
     #
     #Properties
     #
     enableSecurityIntegration=false #boolean,default(false)
     maxWaitTime=5 #integer,default(0)
     context=null
     allowSerializedSessionAccess=false #boolean,default(false)
     enableProtocolSwitchRewriting=false #boolean,default(false)
     enableUrlRewriting=false #boolean,default(false)
     enable=true #boolean,default(false)
     accessSessionOnTimeout=true #boolean,default(true)
     enableSSLTracking=false #boolean,default(false)
     sessionPersistenceMode=NONE #ENUM(DATABASE|DATA_REPLICATION|NONE),default(NONE)
     enableCookies=true #boolean,default(true)
     #
     EnvironmentVariablesSection
     #
     #
     #Environment Variables
     cellName=myCell04
     applicationName=myApp

  2. Run the applyConfigProperties command to create or change a session manager.

     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 '])

• Modify an existing properties file.
  1. Obtain a properties file for the session manager to change.

     We can extract a properties file for an EJBModuleConfig SessionManager object using the extractConfigProperties command.

  2. Open the properties file in an editor and change the properties as needed.

     Ensure the environment variables in the properties file match the system.

  3. Run the applyConfigProperties command.

• If you no longer need the session manager, we can delete the entire session manager object.

  To delete the entire object, specify DELETE=true in the header section of the properties file and run the deleteConfigProperties command; for example:

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

Results

We can use the properties file to manage the session manager 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