Pattern-type (Part 9): Add the capability to Tweak a virtual application instance.

In this previous article ‘Pattern-type (Part 6): How to add operation with SmartCloud Application Services‘, I explained how to add operation on a pattern-type. Operations provide you the ability to take actions on a deployed pattern/virtual application. These actions can be setting parameters and take actions based on these parameters by launching a specified script and this is done by creating an operation.json file in the appmodel. Continue reading

Pattern-type (Part 8): How to extend an existing pattern-type with SmartCloud Application Services

One of my customer asked me the following question:

“I have my own logging event system and I would like that all log files information of the WebSphere Enterprise Application environment are copied to my logging event system. I don’t want to recreate the full WebApp pattern-type just to add a new functionality. So, how can I leverage the existing WebApp pattern-type and add in it just the functionality I need?” Continue reading

Pattern-type (Part 7): Scaling in/out based on OS metrics with SmartCloud Application Services

In my previous articles Pattern-type (Part 5): Scaling in/out based on your own monitoring collector with SmartCloud Application Services I explained how to Scale in/out using your own monitoring collect (ie: counting files in a directory). In noticed in the documentation (IWD Infocenter) at the end of the page a mention of a ‘CPU’ category and ‘Used’ metrics. This let me think we can re-use some embedded OS metrics in a scaling policy and I will show here how to do it. Continue reading

Pattern-type (Part 6): How to add operation with SmartCloud Application Services

When you define a role in a pattern type, you can associate to this role a number of operations you would like to launch once the pattern is deployed. These operations will be available from the ‘Manage’ panel under the operation tab. Continue reading

Pattern-type (Part 5): Scaling in/out based on your own monitoring collector with SmartCloud Application Services

From the Pattern-type (Part 4): Adding your own monitoring collector to a pattern-type with SmartCloud Application Services, we learned how to add a collector to a pattern-type in order to monitor the deployed services. It was a simple collector counting the number of files in a directory. What I propose in this article is to explain how to leverage this collector to add scaling in/out rules based on the metrics provided by this collector. Continue reading

Pattern-type (Part 4): Adding your own monitoring collector to a pattern-type with SmartCloud Application Services

In the previous articles, I explained own to creates pattern-type for a single server, a master-slave and also how to add static scalability to a pattern-type. Now, if we want to have a dynamic scalability, a scalability which react on a monitoring feature, we have to be able to collect information from the server and this exactly what I will explain in this article. Continue reading

Pattern-type (Part 3): Adding Static scalability to a pattern-type with SmartCloud Application Services

In our ongoing journey on the pattern-type elaboration on the SmartCloud Application Services, I explained how to create a simple pattern-type, how to create a master-slave pattern-type, now I will show how to add a static scalability in the master-slave pattern-type. Of Course, this functionality also existing on the PureApplications and IWD. Continue reading

Pattern-type (Part 2): Create step-by-step a Master-Slave pattern-type with SmartCloud Application Workload Services

After having created the Create step-by-step a simple pattern-type with SmartCloud Application Workload Services” article, I challenged myself to create a Master-Slave pattern-type. The main difference consist of creating a link between both servers from the Master to the Slave, and retrieve some information from the Slave (ie: IP address) to configure the Master. Continue reading