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
Tag Archives: #ibmpuresystems
Pattern-type (Part 20): Parametrize a plugin
Sometime, you would like to parametrize a plugin for example to add an activation key or other configuration parameters. The configuration will be done via the “System Plug-ins” menu. Continue reading
Pattern-type (Part 19): internationalization and localization of Pattern-type
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
Using PDK 126.96.36.199 on SmartCloud Application Workload Service
I tested the new version PDK 188.8.131.52 on SmartCloud Application Workload Service which run IWD 184.108.40.206.
Normally, the PDK 220.127.116.11 is compatible with IWD 18.104.22.168 but I didn’t face any issue while using it. Continue reading
Create a mixed language application pattern
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 16): Create a plugin that modify automatically all generated Topology for SCAS
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
Pattern-type (Part 15): How to create a client using Python scripts for a shared service on IBM SmartCloud Application Workload Service
The example provided in the PDK is very clear. The idea is to call the shared service by adding some function in your *.py scripts.
In the PDK example, you will find a Python script call ‘action.py’ which contains all methods in order to call your shared service.
You will need only to change, the name of the shared service.
regInfo = maestro.registry.getRegistry("sample", "1.0") # Retrieve info on SharedService (IP) so we know where to go ipAddr = regInfo['ip'] jsonResults = pcurlInvoke(ipAddr, "sample", method, sslOpts, url, str(json)) # Drive pcurl method
regInfo = maestro.registry.getRegistry("poolmanager", "1.0") # Example to call the poolmanager . ipAddr = regInfo['ip'] jsonResults = pcurlInvoke(ipAddr, "poolmanager", method, sslOpts, url, str(json)) # Drive pcurl method
Pattern-type (Part 14): How to create a client using ServiceProvisioner for a shared service on IBM SmartCloud Application Workload Service
In this article, I explain how to create a simple client for the shared service created in the article Pattern-type (Part 13): How to create shared services for IBM SmartCloud Application Workload Service.
We can call APIs defined by a shared service either from an OSGI component or from python scripts. In this article I will demonstrate the OSGI component method.
We will use as base plugin, the Master-Slave plugin we developed along this education series.
Pattern-type (Part 13): How to create shared services for IBM SmartCloud Application Workload Service
Let’s imagine you would like to manage a pool of resources, each resource are not sharable and thus a pattern can request a resource at deployment time and return the resource during its deletion.
To reach that goal, you can create, what we call, a shared service. The shared service will manage the pool of resources and provide basic functionality such as ‘get a resource’, ‘return a resource’. Continue reading
Reusable assets in IBM PureApplication System and IBM SmartCloud Application Services
This article is also valid for IBM SmartCloud Application Services!
Summary: Reusable components provide a method by which domain experts can capture their knowledge of an enterprise system into reusable components that can be easily consumed by users creating new application patterns. This article describes the use of reusable components and application templates within IBM® PureApplication™ System. Learn about processes that can be used to accelerate the development life cycle and provide consistent implementations across deployments. Continue Reading ->