Category Archives: IBM PureApplication System

Pattern-type (Part 22): Create a component which doesn’t generate a VM.

Posted on by

In the previous article (here), I explained how to create a component that generates one or more VMs. In this one, I will explain a method to create a component which doesn’t generate VM but interacts with another one via a link. You can find a use case of this in the WebApp pattern where you are able to add extra “archive file” to a WAS via the “Extra Archive File” component. Continue reading →

Redbook: Creating Composite Application Pattern Models for IBM PureApplication System

Posted on by

On top of the education series I created (here) you can download a very useful redbook (here) which explains the different concepts and features of the PureApplication System deployment engine which is in fact an IWD software appliance. Continue reading →

Pattern-type (Part 19): internationalization and localization of Pattern-type

Posted on by

When you create a new plugin, you could have noticed that a “locales” directory is created by the plug-in project wizard in the appmodel directory. This directory can contains the messages in different languages. Here how it works. Continue reading →

Pattern-type (Part 18): Create multiple VMs for the same component

Posted on by

I got a question: “Can I create multiple VMs for a given component?”. Imagine you have an application component that needs extra VMs if some policies are set! I don’t want to bother the pattern designer with some extra rules and tell him “if you define this policy you absolutely need to add an extra VM in order to manage this policy”. Continue reading →

Create a mixed language application pattern

Posted on by

Using IBM Mixed Language Application Modernization Pattern
Summary:  Learn how to create a mixed language application pattern using the workload console in IBM PureApplication system. To help you get started building a pattern, templates for deploying COBOL or C applications are provided. As part of this demo a pattern is create that has a web component to invoke a COBOL application.
Continue reading ->

Pattern-type (Part 17): Tips: How to attach a URL to your pattern

Posted on by

Here a very quick tip, when you deploy a WebApp pattern you can see next to the WAS role the URL (Endpoint) to access your deployed app:
SCAWS Web Application Only Status

This can be easily achieved and just by adding a line in your topology template.

1) Locate the role in the roles array for which you would like to add the link.
2) Insert a line like:

"external-uri": [{"ENDPOINT":"http://{SERVER}:8080/${attributes.appURL}"}],

Now, the question is where the {SERVER} comes from?
When we look at the storehouse, we can see that the {SERVER} is still present in the generated topology and thus I have the feeling that this variable is interpreted by the UI as being the IP address of the server where the WAS role has been deployed.
In fact you can insert any parameters defined in the tweak.json between braces and they will be replaced by their value.

Pattern-type (Part 16): Create a plugin that modify automatically all generated Topology for SCAS

Posted on by

Somebody asked me the following question:

“I have to create a framework for future development of pattern-type, each server generated by plugins in this framework must have a specific software when a given role is used. I would like this behavior as much as possible transparent for the developer who use this framework. I think I have to use the TopologyProcessor”. Continue reading →