5 Things To Know About IBM PureApplication System Workload
5GS6_Margaret_Ticknor 1000005GS6 Visits (3489)
The pattern-based deployment approach of IBM PureApplication System has influenced, changed, and revolutionized the relationship between development and system operations, as well as the roles within these teams. IBM has uniquely built expert knowledge into PureApplication System with patterns of expertise.
Here are 5 things to know:
1. Automate your lifecycle steps
IBM PureApplication System Virtual System Pattern instances, have a lifecycle that is managed either by an operations team, a development team or by a combined deve
2. Do not consider environments to be long-lived assets
Existing clients have WebSphere Application Server cells and other system environments whose lifetime is very long, usually it takes a major version upgrade or something of similar magnitude to motivate a team to decommission an environment and create a new one. These are long and complex processes in conventional environments. However, PureApplication System makes the creation of a new environment a fast and painless process. This leads to a major change in the way that environments are viewed based upon the amount of effort required to create or re-create the environment. If all of the important configuration information is stored in a pattern as opposed to only residing in the configuration files of the cell, then it is easier to simply recreate the cell with any significant change to the configuration.
3. Use out-of-the-box images and patterns where applicable
Avoid unnecessary customizing as IBM will release fixes and updates, which can be applied directly to out-of-the-box materials. Every time a new image is created it must be maintained and managed as an individual unit. This means that OS, middleware and other patches must be applied directly to the image. This has an impact on overall management overhead, so there is a trade-off when considering when to extend an existing image. Does the benefit gained by reducing deployment time outweigh the increase in management overhead?
4. Split patterns along key interfaces
How does one determine the right scope of a virtual system pattern or a virtual application pattern? Essentially, a single pattern should contain only components that are directly related to each other and should not contain components that are shared by any components outside the pattern unless all those components are shared. So any changes that happen to the individual applications are localized to the specific patterns that are affected by those changes.
5. Separate the configuration and the application from the topology
Virtual System Patterns should not include purely application-centric information in the scripts that they execute. Instead, that kind of specific information should be read in by the scripts that run in the deployment process as configuration from a shared repository of information, or from instance-specific locations that are specified as part of the deployment process. This encourages reuse of each Virtual System Pattern and also reduces the total number of Virtual System Patterns that must be managed.
For further details and best practices on IBM PureApplication Systems, see the IBM Redbooks publication IBM