Why choose to automate WAS configurations and deployments with UrbanCode Deploy?Automating WebSphere Application Server version configurations and deployments provides these benefits:
- Reduced Risk: Automated, consistent deployments work across correctly configured WebSphere Application Server installations. You can capture WebSphere Application Server configurations and store them for reuse as templates, ensuring you have the correct configuration for your application deployments.
- Repeatable Process: Configurations can be reused to deploy on-demand to any environment. Role-based permissions and quality gates can be incorporated to enable developers and testers to deploy applications into development and test environments on demand. Repeatable processes reduce the need to configure early production environments for testing, freeing WebSphere administrators to focus on maintaining production.
- Consistency: Configuration and security inconsistencies across environments are easily detected and corrected.
- Visibility and traceability: Gather information about application deployments and Websphere Application Server configurations, such as where, when, and by whom.
- Portability: Use the lift and shift concept to move a current WebSphere Application Server instance to the cloud or migrate configurations to a new WebSphere Application Server version. With UrbanCode Deploy, you can automate the use of lift and shift. Capture your WebSphere Application Server configuration, install WebSphere Application Server on the cloud of your choice, and deploy your working configuration onto your running WebSphere Application Server instance.
- Integration: Integrate with provisioning tools, IaaS, PaaS, major cloud providers, and development and testing tools.
- Blueprint Designer: With the blueprinting capability of UrbanCode Deploy, you can generate blueprints of your target environments and quickly reuse them for any cloud. The Blueprint Designer captures your WebSphere Application Server configurations as part of your environment, and you can deploy a fully configured application stack (compute, network, storage, configuration, and applications) to the cloud of your choice.
Migrate older WebSphere Application Server versions to the latest versionMigrate older WebSphere Application Server versions to the latest UrbanCode makes the migration process simpler. The process for migrating to a newer version of WebSphere Application Server is straightforward and enabled by the WebSphere Application Server Configure < https://developer.ibm.com/urbancode/plugin/websphere-application-server-configure/> plug-in. With this plug-in, you can capture your current WebSphere Application Server configuration, convert the data into a template, and then deploy the configuration to a new environment running a newer version of WebSphere Application Server.
Integrate with existing toolchainsUrbanCode Deploy has a large plug-in library that the UrbanCode Deploy development team, business partners, and user community developed. Combine existing plug-ins with the ability to write your own and you can guarantee UrbanCode Deploy a place in your toolchain. UrbanCode Deploy also has integrations with the entire WebSphere portfolio of products, including WebSphere Application Server, Integration Bus, Portal, MQ and Process Server.
How does UrbanCode Deploy work?
The UrbanCode Deploy contains a graphical Process Designer with built-in actions, including deployment automation of applications, WebSphere Application Server configurations, and installation of a WebSphere Application Server instance. The drag-and-drop process designer gives you detail-level control over what to deploy, when, and where. The process designer is populated based on installed plug-ins. The following plug-ins incorporate steps to install, configure, and deploy the WebSphere Application.UrbanCode Deploy. In the Search field, type
WebSphere Application Server.
ExampleTo configure WebSphere Application Server and deploy an application to it, use the Process Editor to add steps from the installed plug-ins.
Configuration data can be 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 more. These groups can be associated with UrbanCode Deploy components. Processes can be created to apply configurations and configuration changes to WebSphere Application Server instances.
The following example demonstrates the Apply process steps in the Process Editor.
- 1. Clean the working directory.
- 2. Download component artifacts, which are the JSON files that contain the configuration data.
- 3. Replace tokens.
- 4. Combine Cell step runs, the step merges all the JSON files in the cell folder.
- 5. Apply the configuration changes. In the example, changes are applied to the cell and then the Deployment Manager configuration.
SummaryAutomating WebSphere Application Server configurations and deployments with UrbanCode Deploy brings these benefits:
- Access to UrbanCode Deploy features, such as:
- Versioning of configuration data
- Tracing changes to configuration
- Knowing in which environments your configuration data has been applied
- The use of available plug-ins, many of which contain samples to help you get started
- The ability to create and use templates for easy promotion across environments
- Comparisons to a “golden configuration” with a live WebSphere instance to detect configuration drift
- Migration from older WebSphere Application Server releases
- Promotion of WebSphere configuration data from on-premises environment to a cloud environment