Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Manual steps prior to using ReleaseBuilder
- Settings that need to be manually synchronized
- Portal Artifacts that need to be manually installed
- Terminology
Sets that need to be manually synchronized
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 IBM® WebSphere® Portal Express property files that change the portal server's behavior (for example, Request IDs or Parallel Portlet Rendering).
|
| Portal Server Runtime | Performance related settings | All documented entries for WebSphere Portal Express 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 Express. They are developed by the customer. |
| J2EE Artifacts | Any IBM WebSphere Application Server configurations | |
| Custom User Registry | Custom User Registry implementation | |
| External Security Manager | Externalized Portal Entitlements |
IBM Tivoli Access Manager for e-business
|
| External Security Manager | Externalized Portal Entitlements | IBM Tivoli Access Manager for e-business |
| 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 | Sample Policy XML configuration files
Theme policies for information |
Portal Artifacts that need to be manually installed
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 librariesCustom User Registry Java Libraries Credential Vault Adaptors Java Libraries Custom Credentials Java Libraries JAAS Login Modules Java Libraries
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. All deliverables of software development are usually artifacts (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 Search and search collections.
- Web Content Management
- Document Repository
- Documents, flows, roles
- Collaboration Components
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 Express. It consists of portal configurations, portal artifacts, and portal extension artifacts. WebSphere Portal Express 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