Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Cloning a WebSphere Portal V6 installation

Save time and ensure consistent, manageable deployments

Marshall Lamb (mlamb@us.ibm.com), Senior Technical Staff Member, WebSphere Portal Architect, EMC
Photo: Marshall Lamb
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.

Summary:  Portal administrators see how to clone an installation of WebSphere Portal V6 that has been configured for specific deployment needs.

Date:  26 Feb 2010 (Published 04 Apr 2007)
Level:  Intermediate

Activity:  4411 views
Comments:  

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

DescriptionNameSizeDownload method
Article in PDF format0711_lamb-CloneWP6install-rev3.pdf556 KBHTTP
Code sampleswp60_cloning_files.zip6.22 KBHTTP

Information about download methods          Get Adobe® Reader®


Biography

Photo: Marshall Lamb

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.

Comments



Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=206256
SummaryTitle=Cloning a WebSphere Portal V6 installation
publish-date=02262010
author1-email=mlamb@us.ibm.com
author1-email-cc=