|When it comes to administration of WebSphere environments, I (and many others) am a big fan of scripting. In my view, any administrative action you carry out with frequency > 1 is ideally suited for a script. The downside to not using scripts (longer configuration times, inconsistent configurations, isolated expertise) is simply too steep in most cases. I also realize that simply saying that you should script is not enough. For some, the learning curve can be a bit daunting. Quite frequently, I talk about our samples gallery or provide posts with embedded scripts in the hopes that I can help flatten out this curve a bit.|
|While these samples can certainly help to speed up your scripting efforts for certain use cases, they are more or less helpful for solving tactical challenges when scripting. If you and your company are embarking down a strategic path that includes beefing up your administrative scripting capability, I would strongly suggest you look at a resource a few of my colleagues pointed me at recently.|
|The resource I am talking about is the wsadminlib.py package referenced here. This python script file is a collection of hundreds of methods that carry out common WebSphere Application Server administrative tasks. The authors carefully constructed these methods with clear method and parameter names. The result is a script resource that can become the foundation for your custom-crafted administrative scripts.|
I recently downloaded the wsadminlib.py script and began constructing WebSphere CloudBurst script packages to utilize it. To say I am impressed would be an understatement. This file makes so many tasks so incredibly simple. Take for instance the creation of an SIBus. That's just a simple call like the following:
wsadminlib.createSIBus(clusterName, nodeName, serverName, SIBusName, scope, secure)
How about associating a shared library with an application or application module? Another one-line call:
wsadminlib.associateSharedLibrary (libName, appName, warName)
Or what about setting a custom property in the webcontainer? You guessed it. One-line:
wsadminlib.setWebContainerCustomProperty(nodeName, serverName, propName, propValue
|This is just an extremely small sample of what the wsadminlib.py includes. As I mentioned earlier, there are hundreds of other methods that carry out various tasks including: installing applications, creating core groups, creating virtual hosts, installing BLAs, creating JMS queues, and much more. If you are looking to beef up your WebSphere Application Server scripting efforts, or if you are just starting, I strongly encourage you to look into and make use of this valuable resource!|
|-- Dustin Amrhein|
A view from the clouds: Cloud computing for developers
with Tags: websphere_application_server X
DKA 0600026VJ2 Tags:  scripting websphere_cloudburst automation websphere_application_ser... 2,443 Visits
DKA 0600026VJ2 Tags:  websphere_application_ser... cloud_computing db2 virtualization websphere_cloudburst virtual_image database hypervisor_edition 2,243 Visits
Acting on announced intentions, IBM WebSphere made the WebSphere Application Server available as an Amazon Machine Image (AMI) on the Amazon EC2 cloud earlier today. The AMI is offered under a development license, so users can try it out with very little cost (only paying EC2 usage charges). This AMI provides users with easy, low-cost access to the fully compliant J2EE application server environment. Users can use this environment as a sandbox for testing and prototyping traditional J2EE applications without making any specific coding allowances in such applications just because they are running in a cloud environment.
I particularly like the way the AMI is configured on startup. After activating an instance, users are supplied with both a single server instance and an administrative agent connected to that single server instance. The administrative agent is a new profile type introduced in WebSphere Application Server 7.0 that allows users to monitor single server installations. This provides a central administration point for what would otherwise be a disparate set of nodes.
In addition to providing the WebSphere Application Server pre-configured and ready to run on EC2, users can also utilize a simple script to create a more customized AMI. For instance, suppose a user activated the standard AMI and then installed custom applications into the WebSphere Application Server environment. Upon making those customizations, the user could create a new AMI that packages not only the WebSphere Application Server, but also their custom applications. The user could then turn around and launch their new AMI, and when activated the WebSphere Application Server environment would also contain their custom applications.
The availability of the WebSphere Application Server as an AMI on Amazon's EC2 complements the recently announced WebSphere Application Server for Developers edition very nicely. They both provide low-cost, low-risk ways for users to experiment with the robust WebSphere Application Server environment. I encourage you to try out one or both of these offerings and give us your feedback here or via Twitter @WebSphereClouds. Stay tuned for more information about these new WebSphere Application Server offerings.
-- Dustin Amrhein
DKA 0600026VJ2 Tags:  private_cloud cloud_computing websphere_virtual_enterpr... websphere_application_ser... websphere_cloudburst 2,906 Visits