E Labeling During WebCenter Portal Lifecycle

This appendix describes how to use internal labels to keep portal instances, such as stage and production portals, in-sync. You can only propagate portal changes to another portal instance when their internal labels match.

Every portal deployment maintains an internal label. Whenever you deploy or propagate a portal to another server, the source portal's label is copied to the target along with the portal. Similarly, if you deploy a portal to an archive (for export or back up purposes), the portal's label is included within the .par file.

Table E-1 illustrates a labeling scenario where a Sales portal is deployed from stage to production, followed by subsequent propagations and redeployments between stage and production.

Note:

Portal archive exports contain a label with the pattern PTL_ or PTLEXPPORTAL_ depending on which phases a portal goes through. Portals that undergo at least one deployment contain the PTL_ label pattern. Portals that are not yet deployed (when exported) contain the PTLEXPPORTAL_ label pattern.

Table E-1 Internal Labeling on Portal Deployment and Propagation

Step Action Labels in Stage Labels in Production

1

Deploy the Sales portal on stage to production

Use WLST command deployWebCenterPortal

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_1_user
       

2

Change the Sales portal on the stage and propagate changes to production

Use WLST command propagateWebCenterPortal

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user
       

3

Redeploy the Sales portal on stage to production

Use WLST command deployWebCenterPortal

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-
       

4

Propagate Sales portal changes on stage to production

Use WLST command propagateWebCenterPortal

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTL_GUID_#$#_4_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTL_GUID_#$#_4_user
       

5

Back up the production portal

Use WLST command exportWebCenterPortals

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTL_GUID_#$#_4_user

-

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTL_GUID_#$#_4_user

PTLEXPPORTAL_GUID_#$#_1_user
       

6

Back up the stage portal

Use WLST command exportWebCenterPortals

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTL_GUID_#$#_4_user

-

PTLEXPPORTAL_GUID_#$#_3_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTL_GUID_#$#_4_user

PTLEXPPORTAL_GUID_#$#_1_user

-
       

7

Propagate Sales portal changes on stage to production

Use WLST command propagateWebCenterPortal

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTL_GUID_#$#_4_user

-

PTLEXPPORTAL_GUID_#$#_3_user

PTL_GUID_#$#_5_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTL_GUID_#$#_4_user

PTLEXPPORTAL_GUID_#$#_1_user

-

PTL_GUID_#$#_5_user
       

8

Corruption in production so restore the production Sales portal from the latest backup archive (created in step 5)

Use WLST command importWebCenterPortals

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTL_GUID_#$#_4_user

-

PTLEXPPORTAL_GUID_#$#_3_user

PTL_GUID_#$#_5_user

-

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTLEXPPORTAL_GUID_#$#_1_user

-

-

-

PTL_GUID_#$#_4_user
       

9

Propagate Sales portal changes on stage to production

Use WLST command propagateWebCenterPortal

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTL_GUID_#$#_4_user

-

PTLEXPPORTAL_GUID_#$#_3_user

PTL_GUID_#$#_5_user

-

PTL_GUID_#$#_6_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTLEXPPORTAL_GUID_#$#_1_user

-

-

-

PTL_GUID_#$#_4_user

PTL_GUID_#$#_6_user
       

10

Corruption in the stage, so restore the stage Sales portal from the latest backup archive (created in step 6)

Use WLST command importWebCenterPortals

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTLEXPPORTAL_GUID_#$#_3_user

-

-

-

-

-

PTL_GUID_#$#_4_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTLEXPPORTAL_GUID_#$#_1_user

-

-

-

PTL_GUID_#$#_4_user

PTL_GUID_#$#_6_user

-
       

11

Propagate Sales portal on stage to production

Propagation fails because the portal on production is newer than the version on stage.

Either redeploy the Sales portal or restore the production portal on stage (as per steps 12 and 13).

-
       

12

Export the Sales portal from production

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTLEXPPORTAL_GUID_#$#_3_user

-

-

-

-

-

PTL_GUID_#$#_4_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTLEXPPORTAL_GUID_#$#_1_user

-

-

-

PTL_GUID_#$#_4_user

PTL_GUID_#$#_6_user

-

PTLEXPPORTAL_GUID_#$#_2_user
       

13

Restore the Sales portal on stage from the Sales portal archive exported from production (in step 12)

PTL_GUID_#$#_1_user

PTLEXPPORTAL_GUID_#$#_1_user

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

PTLEXPPORTAL_GUID_#$#_2_user

PTLEXPPORTAL_GUID_#$#_3_user

-

-

-

-

-

PTL_GUID_#$#_4_user

-

PTL_GUID_#$#_6_user

PTL_GUID_#$#_1_user

-

PTL_GUID_#$#_2_user

PTL_GUID_#$#_3_user

-

PTLEXPPORTAL_GUID_#$#_1_user

-

-

-

PTL_GUID_#$#_4_user

PTL_GUID_#$#_6_user

-

PTLEXPPORTAL_GUID_#$#_2_user

-

The labels are for internal use only so there is no need for you to view or manage these labels. If there is a mismatch between the source and target labels an error message displays. For example:

Scenario 1: You attempt to propagate a portal that was not previously deployed on the target. The following message displays because the portal's initial deployment label is missing from the target:

Internal label for deployment for the portal <portal_name> does not exist on the target. Ensure that the portal is deployed on the target.

Scenario 2: You attempt to propagate a portal but the label on the target does not exist on the source. The following message displays because the label in the source is lower than the target label:

Cannot propagate the portal. Internal labels in the source and target for portal {0} do not match. Redeploy the portal on the target to synchronize the portals before attempting further propagation.

The type of mismatch can occur if the source portal was restored with an earlier label than the target.