Launch the WorklightStarter sample pattern on SCAWS

This article explains how to launch the WorklightStarter sample pattern on the IBM SmartCloud Application Workload Service. It is part of a series of articles concerning the “IBM Worklight usage on IBM SmartCloud Application Services”. Go on Worklight Trial on SmartCloud Application Service page to get register! Continue reading

Import “IBM Mobile Application Platform Pattern Type” and the sample pattern into SCAWS

This article explains how to import the Worklight pattern type and pattern on the IBM SmartCloud Application Workload Service. It is part of a series of articles concerning the “IBM Worklight usage on IBM SmartCloud Application Services”. Go on Worklight Trial on SmartCloud Application Service page to get register! Continue reading

How to enable IBM SmartCloud Application Services in the Worklight Trial

I will explain in this article how to provision the different services provided by IBM SmartCloud Application Services, which is GA and also in trial (visit the SCAS website for more information on the SCAS trial). Go on Worklight Trial on SmartCloud Application Service page to get register! Continue reading

Load the WorklightStarter sample application on Worklight Studio

This article explains how to import the WorklightStarter project into your Worklight Studio installation. This is part of a series of article explaining the usage of the “IBM Mobile Application Platform Pattern” on the IBM SmartCloud Application Service. Go on Worklight Trial on SmartCloud Application Service page to get register! Continue reading

Use “SCAWS pattern deployer” on Eclipse to deploy pattern and applications (v1.1.1)

I just released a version of the “SCAWS pattern deployer” plugin which allows you to deploy SCAWS pattern from Eclipse (Video available)

– Bug Fix: A Bug prevented to deploy EAR, WAR, ZIP… FILE was ok.

– Bug Fix: New files composing EAR, WAR, ZIP wasn’t detected correctly.

– Improve error handling.

– Remove navigation in the context menu.

Continue reading

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

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

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

by

    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