Starting with version 14 of the WebSphere Application Server – Configure plug-in for IBM UrbanCode Deploy, you can use JSON files to manage WebSphere Application Server configuration.
The configuration data is stored in a series of JSON files. The JSON files can be grouped to represent cell and Deployment Manager configurations, node and node agent configurations, cluster and cluster member configurations, and configurations for other WebSphere objects. You can then associate the groups of JSON files with IBM UrbanCode Deploy components, which allow for assigning versions to the JSON files. Finally, you can create processes to apply configurations and configuration changes to WebSphere Application Server instances.
- Scope-specific application of changes
Because you can group JSON files into components such as cell configuration, node configuration, and other configurations, you can apply changes for one component without affecting the other components. For example, you can choose to apply only cell configuration changes. Changes to the cell configuration are then applied, but the node configuration remains unchanged.
- Version comparison
Because the JSON files are stored as component artifacts, they are assigned versions. You can compare versions to identify configuration changes by using the IBM UrbanCode Deploy user interface.
- Template creation for multiple clusters and environments
You can build a JSON template that represents a server cluster member. Users can then create any number of server cluster members based on the template. For example, in a development environment, users might want to deploy a cluster with two servers on each node. In a QA environment, each cluster might contain four servers. You can use the JSON server template with IBM UrbanCode Deploy to create these multiple servers.