 | Level: Intermediate Marshall Lamb (mlamb@us.ibm.com), Senior Technical Staff Member, WebSphere Portal Architect, IBM
04 Apr 2007 Updated 22 Jan 2008
Portal administrators see how to clone an installation of IBM® WebSphere® Portal V6 that has been configured for specific deployment needs. You learn to copy your own standardized installation of WebSphere Portal and use it as a template to mass-produce additional pre-installed and pre-configured portals. In this article
- Understand prerequisites
- Review various considerations and limitations
- Build the WebSphere Application Server Custom Install Package (CIP)
- Build the installation archive
- Create a WebSphere Portal installation from an archive
- Automate the process
Background
It's one thing to install a basic WebSphere Portal system; you could finish this task in one to two hours. However, It's a whole other matter to establish a complete portal enviornment that meets internal security configuration requirements, connects to the corporate LDAP and database servers, and includes all the portal’s basic set of pages and portlets; for this task, you should plan several extra days. Administrators who need to establish multiple environment could benefit from being able to replicate a base, fully-configured portal enviornment quickly. This article can help you do just that. You learn how to build a custom install package, archive the install, and then use that archive as a template for creating addiitonal installations. Finally, you see sample code for automating much of the process.
Downloads | Description | Name | Size | Download method |
|---|
| Article in PDF format | 0711_lamb-CloneWPInstall.pdf | 556 KB | HTTP |
|---|
| Code samples | localize_clone.zip | 4 KB | HTTP |
|---|
About the author  | 
|  |
Marshall Lamb is a Senior Technical Staff Member and Software Architect for WebSphere Portal. He was previously the Chief Programmer for WebSphere Portal for several years. Marshall started in networking software development, working through the Host Integration product line, before moving into the Pervasive Software Division (WTP), and finally into Lotus Software with WebSphere Portal. |
Rate this content
|  | |  |