Manual steps prior to using ReleaseBuilder

 

+
Search Tips   |   Advanced Search

 

  1. Checklist: Properties
  2. Checklist: Portal Artifacts
  3. Terminology

 

Checklist: Properties

The following list contains all configurations that need to be manually synchronized between the systems involved in a staging to production process. These settings are neither covered by the XML configuration interface nor staged by other tools.

Component Property Description
Portal Server Runtime Portal System Configuration All documented entries for portal property files that change the portal server's behavior. For example, Parallel Portlet Rendering
Portal Server Runtime Performance related settings All documented entries for WebSphere Portal property files, excluding settings related to environment scaling.
Portal Statistics Statistics Log Settings  
Portlet Services Service configuration
Custom Login Commands Login command
Custom Credential Vault Adaptors Vault Adaptors
Custom Credentials Credential Implementations
JAAS Login Modules Custom modules
Custom components Custom component property files These components are not part of WebSphere Portal. They are developed by the customer.
J2EE Artifacts Any IBM WAS configurations
Custom User Registry Custom User Registry implementation
External Security Manager Externalized Portal Entitlements

External Security Manager

(IBM Tivoli Access Manager for e-business )

Externalized Portal Entitlements  
User Directory User Profiles, Groups LDAP: Configuration movement functions are provided by the product vendor or implementer.
Document Manager Documents and Roles  
Personalization Personalization rules and Campaigns Refer to Personalization topics in the information center for information about publishing.
Policies Policy files Refer to Theme policies for information

 

Checklist: Artifacts

The following list contains all portal artifacts that need to be manually installed on each system involved in the staging to production process. The installation instructions for each artifact can be found in the information center.

Artifact Type
Portlets WAR files
Themes JSPs, Images, CSS. etc.
Skins JSPs, Images
Portal Screens JSPs and Images
Portlet Services Java Libraries
J2EE Artifacts EAR files

Java libraries

Custom User Registry Java Libraries
Credential Vault Adaptors Java Libraries
Custom Credentials Java Libraries
JAAS Login Modules Java Libraries

For information on installing WebSphere Portal to set up the staging server see Installing and configuring. For information on moving a staging server to production, including import and export commands, see Sample file ExportRelease.xml.

 

Terminology

Staging is the process of moving solution releases from development to production. This process typically consists of partially or fully automated configuration management tasks and quality assurance activities.

 

Portal Artifacts

Portal Artifacts are stored in the portal file system.

Software deliverables are generally artifacts, unless otherwise referred to as software components.

The following components are portal artifacts...

Portal System Configuration Property files
Themes and Skins JSP files and stylesheets
Portal Customizations Java Classes
Portlet services
Active Credentials
Credential VaultAdaptors
Portlet Code Java Classes
JSPs
XML files
Portal Filters Java Classes
Servlet Filters Java Classes
J2EE Artifacts Managed by WebSphere Application Server

 

Portal Extension Artifacts

Portal Extension Artifacts are stored in the portal file system or in a database. These artifacts exist in an installed portal system. They belong to components that are installed together with the portal but are not core portal components. Typically these components are available with and without the portal server.

The following components are examples of portal extension artifacts:

 

Portal Configuration

The Portal Configuration is stored in the portal configuration database. It consists of configuration entities. Each portal resource is represented by one portal configuration entity in the portal database.

The following entities are part of the portal configuration:

  • Portal Content Tree (Navigation, Pages, Layouts)
  • URL Mappings
  • Portlet Application Configurations
  • Portlet Application Settings
  • Portlet Configurations
  • Portlet Settings
  • Portlet Data (legacy portlets)
  • Portlet Preferences (JSR168 portlets)
  • Access Control Data (Roles, ActionSets)
  • Credential Data
  • Themes
  • Skins

 

Portal Solution Release

The Portal Solution Release is the solution that is developed by you, the customer, on top of WebSphere Portal. It consists of portal configurations, portal artifacts, and portal extension artifacts. WebSphere Portal is not part of the Portal Solution Release. The Portal Solution Release configuration is shared between multiple users, user configurations are not included. Administrators create and maintain the portal solution configurations.

 

Parent topic:

Staging to production

 

Related concepts

About ReleaseBuilder
Overview of staging the portal to production
Staging the portal to production

 

Related tasks


Building a Release