Introducing Properties File Based Configuration - A way to automate WebSphere configuration changes without extensive scripting skills (Part 1)
Yan Zhao 110000MGDP Visits (10084)
by Yan Zhao and Sangwon Oh
Imagine that you are a WebSphere administrator who does not have a lot of scripting experience. Due to recent changes you need to modify a set of specific configurations or copy a set of properties from one environment to another or move large number of configuration objects to a different scope in the cell, etc. Manually going through panel by panel in the Administration console would be very tedious and error prone. Writing your own scripts might be time consuming. Properties File Based Configuration is an easy and efficient way to help you accomplish those tasks.
1. You cannot extract whole configuration properties from one cell, and apply to another empty cell to clone your environment. Both cells need to be identical with the same number of servers, nodes, clusters, and so on with the same name. But, if you want to copy a subset of configuration from one cell to another cell (for example, Data Source, J2CResourceAdapter, so on) it will work. In this case, the properties file extracted from one cell can be used to create similar configuration objects in another cell.
2. You cannot apply an z/OS operating system properties file to a distributed operating system. Similarly, you cannot apply a distributed operating system properties file directly to a z/OS operating system.
3. Following configurations cannot be configured using properties file.
The Properties file based configuration helps you to customize configurations that are created based on WCCM or configurations that are deployed as J2EE applications. You can use properties files to customize configuration (not clone or merge environments).
Some example usage:
Here are the commands for Properties file based configuration:
We will go into more details on what each command does in Part 2 of this topic.