Scripting to ease WebSphere Portal deployments (part 1)

by Damian Langsweirdt, Senior Consultant, Ascendant Technology

When creating a WebSphere Portal solution, developers are often tempted to write the code, test it, and hand off a multipage document (outlining the deployment steps) to a WebSphere administrator. For example, certain datasources or JNDI variables may need to be created, certain pages in the portal may need to be created and populated, and various portlet applications deployed. Creating a document with several steps is tempting because it is easy (for the developer); however, there is a risk that these manual steps will be skipped or performed incorrectly, and there is a repeated cost for each new environment to which the application will be deployed.

Electronic license holders click here to access full article.

Would you like to see the full version of this and every article? Click here to subscribe.

This article is available as part of The Sphere e-Newsletter on Portal. Click here to register for non-subscriber access.