You can use the Jython scripting language to manage your system configuration using properties files. Use the commands in the PropertiesBasedConfiguration group to copy configuration properties from one environment to another, troubleshoot configuration issues, and to apply one set of configuration properties across multiple profiles, nodes, cells, servers, or applications.
The applyConfigProperties command applies properties in a specific properties file to the configuration. The system adds attributes or configuration data to the configuration if a specific properties do not exist. If the properties exist in the configuration, the system sets the new values for the attributes.
Target object
None.
Required parameters
Optional parameters
Return value
The command does not return output.
Batch mode example usage
AdminTask.applyConfigProperties('-propertiesFileName myPropFile.props -zipFileName myZipFile.zip -validate true')
AdminTask.applyConfigProperties(['-propertiesFileName', 'myPropFile.props', '-zipFileName', 'myZipFile.zip', '-validate', 'true'])
Interactive mode example usage
AdminTask.applyConfigProperties('-interactive')
The createPropertiesFileTemplates command creates template properties files to use to create or delete specific object types. The command stores the template properties file in the properties file specified by the propertiesFileName parameter.
Target object
None.
Required parameters
Optional parameters
NoneReturn value
The command does not return output.
Batch mode example usage
AdminTask.createPropertiesFileTemplates('-propertiesFileName serverTemplate.props -configType Server')
AdminTask.createPropertiesFileTemplates(['-propertiesFileName', 'serverTemplate.props', '-configType', 'Server'])
Interactive mode example usage
AdminTask.createPropertiesFileTemplates('-interactive')
The deleteConfigProperties command deletes properties in your configuration as designated in a properties file. The system removes the attributes or configuration data that corresponds to each property in the properties file.
Target object
None.
Required parameters
Optional parameters
Return value
The command does not return output.
Batch mode example usage
AdminTask.deleteConfigProperties('-propertiesFileName myPropFile.props')
AdminTask.deleteConfigProperties(['-propertiesFileName', 'myPropFile.props'])
Interactive mode example usage
AdminTask.deleteConfigProperties('-interactive')
The extractConfigProperties command extracts configuration data in the form of a properties file. The system exports the most commonly used configuration data and attributes, converts the attributes to properties, and saves the data to a file. You can specify the resource of interest with the target object or the configData parameter. Use the configData parameter to specify a server, node, cluster, policy set, or application instance. If no configuration object is specified, the command extracts the profile configuration data.
Target object
Specify the object name of the configuration object of interest in the format: Node=nodeName:Server=serverName
Required parameters
Optional parameters
Configuration object type | Subtypes | Extensions |
---|---|---|
AdminService | None | None |
Application | JDBCProvider,VariableMap | None |
ApplicationServer | TransactionService, DynamicCache, WebContainer, EJBContainer, PortletContainer, SIPContainer, WebserverPluginSettings | None |
AuthorizationGroup | None | None |
AuthorizationTableExt | None | None |
Cell | VirtualHost, DataReplicationDomain, ServerCluster, CoreGroup, NodeGroup, AuthorizationGroup, AuthorizationTableExt, Security, J2CResourceAdapter, JDBCProvider, JMSProvider, MailProvider, URLProvider, EventInfrastructureProvider, ObjectPoolProvider, WorkManagerProvider, TimerManagerProvider, SchedulerProvider, Node, VariableMap | None |
CoreGroup | None | None |
CoreGroupBridgeService | None | None |
DynamicCache | None | None |
EJBContainer | None | None |
EventInfrastructureProvider | None | None |
EventInfrastructureService | None | None |
HAManagerService | None | None |
J2CResourceAdapter | None | None |
JDBCProvider | None | None |
JMSProvider | None | None |
JavaVirtualMachine | None | None |
Library | None | None |
MailProvider | None | None |
NameServer | None | None |
Node | Server, J2CResourceAdapter, JDBCProvider, JMSProvider, MailProvider, URLProvider, EventInfrastructureProvider, ObjectPoolProvider, WorkManagerProvider, TimerManagerProvider, SchedulerProvider, VariableMap | The NodeMetadata Extension extracts node Metadata properties. |
NodeGroup | None | None |
ObjectPoolProvider | None | None |
ObjectRequestBroker | None | None |
PMEServerExtension | None | None |
PMIModule | None | None |
PMIService | None | None |
PortletContainer | None | None |
SIPContainer | None | None |
SchedulerProvider | None | None |
Security | None | None |
Server | PMIService, AdminService, CoreGroupBridgeService, TPVService, ObjectRequestBroker, ApplicationServer, NameServer, J2CResourceAdapter, JDBCProvider, JMSProvider, MailProvider, URLProvider, EventInfrastructureProvider, ObjectPoolProvider, WorkManagerProvider, TimerManagerProvider, SchedulerProvider, VariableMap, EventInfrastructureService, PMEServerExtension, Library, HAManagerService, PMIModule, Security | The extension lists deployed applications for a specific server. |
ServerCluster | J2CResourceAdapter, JDBCProvider, JMSProvider, MailProvider, URLProvider, ObjectPoolProvider, WorkManagerProvider, TimerManagerProvider, SchedulerProvider, VariableMap | The extension lists deployed applications for a specific cluster. |
TPVService | None | None |
TimerManagerProvider | None | None |
TransactionService | None | None |
URLProvider | None | None |
VariableMap | None | None |
VirtualHost | None | None |
WebContainer | None | None |
WebserverPluginSettings | None | None |
WorkManagerProvider | None | None |
Return value
The command returns the name of the properties file that the system creates.
Batch mode example usage
AdminTask.extractConfigProperties('-configData Node=myNode -propertiesFileName myNodeProperties.props -zipFileName myZipFile.zip')
AdminTask.extractConfigProperties(['-configData', 'Node=myNode', '-propertiesFileName', 'myNodeProperties.props', '-zipFileName', 'myZipFile.zip'])
Interactive mode example usage
AdminTask.extractConfigProperties('-interactive')
The validateConfigProperties command verifies that the properties in the properties file are valid and can be successfully applied to the new configuration.
Target object
None.
Required parameters
Optional parameters
Return value
The command returns a value of true if the system validates the properties file or policy set .zip file.
Batch mode example usage
AdminTask.validateConfigProperties('-propertiesFileName myNodeProperties.props -zipFileName myZipFile.zip -reportFileName report.txt')
AdminTask.validateConfigProperties(['-propertiesFileName', 'myNodeProperties.props', '-zipFileName', 'myZipFile.zip', '-reportFileName', 'report.txt'])
Interactive mode example usage
AdminTask.validateConfigProperties('-interactive')