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 > Work with mail provider properties files

Work with mail session properties files

We can use properties files to create or change mail session properties.

Determine the changes to make to your mail session configuration or its configuration objects.

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 a mail session object and its configuration properties.

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

Actions for mail session properties files. We can create, modify, and delete mail session configuration properties.

Action	Procedure
create	Set properties and then run applyConfigProperties.
modify	Edit properties and then run applyConfigProperties.
delete	Uncomment #DELETE=true and run deleteConfigProperties.

Optionally, you can use interactive mode with the commands:

AdminTask.command_name('-interactive')

Procedure

• Create a mail session and its properties.

  1. Create a properties file for a MailSession object.

     Open an editor and create a mail session properties file. We can copy an example properties file in this step into an editor and modify the properties as needed for your situation.

     The following example defines a mail session with jndiName myJndiName under a mail provider named Built-in Mail Provider at cell scope:

     #
     # Header
     #
     ResourceType=MailSession
     ImplementingResourceType=MailSession
     ResourceId=Cell=!{cellName}:MailProvider=Built-in Mail Provider:MailSession=jndiName#myJndiName
     #DELETE=true
     #
     
     #
     #Properties
     #
     mailStorePort=0 #integer,default(0)
     mailFrom=null
     mailTransportPort=0 #integer,default(0)
     mailStoreHost=null
     providerType=null
     mailTransportHost=null
     mailStorePassword=null
     debug=false #boolean,default(false)
     mailStoreUser=null
     category=null
     description=myJndiName #required
     mailTransportUser=null
     ObjectName=null
     mailStoreProtocol=null
     provider=Built-in Mail Provider #ObjectName(MailProvider),readonly
     String=null
     mailTransportPassword=null
     strict=true #boolean,default(true)
     name=myName #required
     
     
     EnvironmentVariablesSection
     #
     #
     #Environment Variables
     cellName=WASCell06
     nodeName=WASNode04
     

  2. Run applyConfigProperties to create a mail session configuration.

     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 mail session.
  1. Obtain a properties file for the mail session that you want to change.

     We can extract a properties file for a MailSession object using the extractConfigProperties command.

  2. 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.

  3. Run applyConfigProperties to change a mail session configuration.

• If you no longer need a mail session, you can delete the entire mail session 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 mail session object.

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

+

Search Tips   |   Advanced Search