WAS v8.5 > Script the application serving environment (wsadmin) > Use properties files to manage system configuration > Manage specific configuration objects using properties files

Work with JDBC provider properties files

We can use properties files to create, modify, or delete JDBC provider properties.

Determine the changes to make to your JDBC provider configuration or its configuration objects.

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 JDBC provider object.

Run administrative commands using wsadmin to apply a properties file for a JDBC provider to your configuration, validate the properties, or delete them.

Actions for JDBC provider properties files. We can create, modify, and delete JDBC provider properties.

Action	Procedure
create	Set required properties and then run the applyConfigProperties command.
modify	Edit required properties and then run the applyConfigProperties command.
delete	To delete the entire JDBCProvider 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 JDBCProvider properties file.

  1. Set JDBCProvider properties as needed.

     Open an editor on a JDBCProvider properties file. Modify the Environment Variables section to match the system and set any property value that needs to be changed. An example JDBCProvider properties file follows:

     #
     # Header 
     #
     ResourceType=JDBCProvider
     ImplementingResourceType=JDBCProvider
     ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}:JDBCProvider=myJDBCProvider
     #DELETE=true
     #
     
     #
     #Properties
     #
     classpath={${DERBY_JDBC_DRIVER_PATH}/derby.jar}
     name=myJDBCProvider
     implementationClassName=org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource
     nativepath={}
     description=Derby embedded non-XA  JDBC Provider #providerType=Derby JDBC Provider #readonly
     xa=false #boolean
     
     EnvironmentVariablesSection
     #Environment Variables
     cellName=myCell
     nodeName=myNode
     serverName=myServer

  2. Run the applyConfigProperties command to create or change a JDBC provider 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'])

• Modify an existing properties file.
  1. Obtain a properties file for the JDBC provider to change.

     We can extract a properties file for a JDBCProvider 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 JDBC provider, we can delete the entire JDBC provider 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 JDBC provider object and its properties.

Save the changes to your configuration.

Subtopics

• Work with data source properties files
  We can use properties files to create, modify, or delete data source properties.
• Work with CMP connection factory properties files
  We can use properties files to create, modify, or delete container managed persistence (CMP) connection factory properties.

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