The source system requires the following items to be configured:

• A batch user account. This user allows publishing to run as a background process and designates the location of publishing logs.

• If there is a proxy, the identity of the local proxy server. This is identified to WebCenter Sites in the wcs_propeties.json file.

• For large publishes (such as the initial publication of a site), the session timeout may have to be increased beyond the default 900 seconds (for example, 9000 seconds). To do so, open the Property Management Tool in the Admin interface and change cs.timeout to 9000, then restart WebCenter Sites. When the publish is completed this value can be reset.

• The publishing destination, which identifies:

  • The destination URL and port

  • The publishing method

  • Publishing log and email notification options

  • User roles with approval and publishing privileges

  • The RealTime user, who has publishing privileges on the destination

<http>
    <server-header>default</server-header>
    <max-unchunk-size>102400000</max-unchunk-size>
    <unchunk-timeout>-1</unchunk-timeout>
    <io-timeout>600</io-timeout>
<http>

Additionally, though not required for publishing to work, you can configure a publishing schedule which will publish approved assets on a regular basis.

The destination system requires the following items to be configured:

• A RealTime user account, which has publishing privileges on the destination.

• Mirrored site configuration data from the source system for the sites to publish:

  • WebCenter Sites

  • Publication and SitePlanTree table data

  • Auxiliary tables (such as Source and MimeType)

  • Asset types

  • Roles

  • Start menu items *

  • Workflow groups and processes *

  • Tree tabs *

  • Saved searches *

  Items marked with an asterisk are typically not necessary on a delivery system.

If you will not publish from the destination system, we recommend turning off asset invalidation.

1. Log in to the Admin interface on your source system.
2. In the General Admin tree, expand the User Access Management node, and then double-click User.
3. Create a user account for the publishing system on the source system to use (that is, the batch user) and assign it the following ACLs:

   • Browser

   • ElementEditor

   • PageEditor

   • TableEditor

   • UserReader

   • Visitor

   • VisitorAdmin

   • xceladmin

   • xceleditor

   If you require help with this step, see Creating a User in the Admin Interface.

4. Open the Property Management Tool:

   In the General Admin tree, expand the Admin node, expand the System Tools node, and then double click Property Management.

   Note:

   For information about using the Property Management Tool, see the Properties in the Publish Category in Property Files Reference for Oracle WebCenter Sites.

5. In the Category drop-down menu, select Publish.
6. Click Search.
7. Set values for the following properties:

   • xcelerate.batchhost

     Set this property to the host name of the application server that is hosting the source system. The source system is the batch host. If the port number of the web server is anything other than 80, you must also include the port number. For example, myserver:7001. In a clustered WebCenter Sites environment, only one batch host is supported. The xcelerate.batchhost property must be set on each cluster member to point to the dedicated host.

   • xcelerate.batchuser

     Set this property to the name of the user that you created in step 3 of this procedure.

   • xcelerate.batchpass

     Set this property to the password of the user that you created in step 3 of this procedure.

   • request.folder

     Point this property to the directory to hold your publish log files. By default, this property is set to the dispatcher subdirectory in the application server installation directory.

     Note:

     Be sure to set this property to a directory that can be written to. Otherwise, no session information is shown in the Publish History tab of the Publish Console.

8. Restart the application server.

1. Determine which auxiliary tables on the source system support the types of assets that users will publish, then manually re-create the table structure on the destination system.

   Note:

   Auxiliary tables are custom-defined tables that support asset types. The tables are not created using WebCenter Sites AssetMaker or Flex Family Maker. Examples of auxiliary tables are Source, MimeType, and lookup tables (for different attributes in asset types).

   Database properties on the source and destination systems, if not an exact match, must be compatible, particularly database schema options (in the wcs_properties.json file, set from the Property Management Tool). Be sure to restart the application server if you make changes to database schema properties.

2. Create the RealTime user on the destination system (using the administrator's interface) and note the following:

   Note:

   The RealTime user has the same privileges as the mirror user configured for Mirror to Server publishing. If a mirror user is configured for Mirror to Server publishing, the same user could serve as the RealTime user.

   • Basic privileges: The RealTime user must be assigned the following ACLs:

     • Browser

     • ElementEditor

     • PageEditor

     • TableEditor

     • Visitor

     • VisitorAdmin

     • xceladmin

     • xceleditor

   • Additional privileges: Because the RealTime user account is used by the CacheManager to regenerate the page cache after a publishing session, the RealTime user must have sufficient privileges to regenerate all the pages in the cache. Therefore, the RealTime user account must be assigned all the ACLs that are assigned to page entries in the SiteCatalog table or database tables that hold data to be rendered.

   If you require help with creating the mirror user, see Creating a User in the Admin Interface.

This procedure must be performed only one time on each source system, regardless of the number and types of publishing destinations you are configuring.

If the local proxy has been identified to your source system, or a proxy server is not used, skip to Creating a RealTime Destination Definition on the Source System.

To identify a proxy server to the source system, see one of the following topics:

• Identifying the Local Proxy Server to the Source System for All Destinations

• Identifying the Local Proxy Server to the Source System Per Destination

1. On the source system, log in to the administrator's interface.
2. In the General Admin tree, expand the Admin tree, expand the Publishing node, and expand the Destinations node.
3. Under the Destinations node, double-click Add New.

   The Add New Destination form opens.

4. Fill in the Add New Destination form. For guidelines, use the information below.

   • Name: Enter a unique name for the destination.

     Note:

     The following characters are not allowed in the Name field: single quote ('), double quote ("), semicolon (;), colon (:), less-than sign (<), greater-than sign (>), percent (%), and question mark (?). Additionally, the name cannot end with a backslash (\).

   • Delivery Type: Select RealTime: Copy assets to remote dynamic server, then choose an option:

     • Complete publish to copy assets to the destination address without interruption to the publishing process.

     • Delayed publish to pause the publishing process before assets are committed to the destination database. To resume the session, a user must initiate the fourth stage of publishing (deserializing [inflating] data and saving it to the destination database). See Resuming a Delayed Publishing Session.

   • Destination Address: Enter the URL in the format shown. For [targetserver:port], delete the brackets, enter the host name or IP address of the destination system, and specify the port to be used by the destination. (A slash is required after the URL because this URL is appended dynamically.)

   • Remote User: Enter the name of the RealTime user that you created in Setting Up the Destination System. This user is called by the publishing system to unpack the RealTime queue on the destination system.

   • Remote Password: Enter the password of the RealTime user.

   • Send Email on Failure: If publishing fails and email notices to that effect are required, select the check box and fill in the field that opens:

     • EmailIDs: Enter the recipient's email address. (This field is available only when Send Email on Failure is selected.)

   • Verbose Output: Select this option to activate detailed error logging during the publishing process. When this option is selected, messages in addition to error messages are written to the PubMessage table. Because additional information lengthens the publishing process, select this parameter only for troubleshooting.

   • More Arguments: This parameter is reserved; no additional arguments can be specified at this time.

   • Sites: Select the sites whose assets can be approved for and published to this destination.

   • Roles (Approve for Publish): Select the roles to which you are assigning asset approval privileges. All users assigned these roles are able to approve assets.

   • Roles (Publish): Select the roles to which you are assigning publish privileges. All users assigned these roles are able to publish and view the Publish Console.

5. Click Add New Destination.

   WebCenter Sites writes your information to the Pubdestination table and displays the destination definition in the Inspect form:

   Figure 16-3 Publish Destination Form

   
   Description of "Figure 16-3 Publish Destination Form"

   Note:

   A red button next to the destination name means that the target server cannot be located. Common causes are the target URL is incorrect or the target server is not running.

6. To create more destination definitions, repeat steps 3 through 5 for each new definition.
7. When you are ready to initialize the destination system, proceed to the next section, Initializing the Destination Database. Begin at step 3 of that procedure.

1. In the General Admin tree on the source system, expand the Admin node, expand the Publishing node, expand the Destinations node.
2. Under Destinations node, double-click the RealTime destination you want to initialize.
3. In the Publish Destination form, click Initialize RealTime Destination.

   The Initialize RealTime Destination form opens.

4. In the Sites field, select the sites whose assets you want to publish to this destination.
5. In the Auxiliary Tables field, enter the names of the following tables:

   • Source, if you are using the source feature for any of your asset types.

   • MimeType, if you are using flex filter assets, the ImageFile asset type, or if you are using the MimeType table for any of your custom asset types.

   • Filters, if you are using flex filters on your site. (The Filters table lists the classes that are used by the flex filters. You will have to copy jar files and classes manually.)

   • Any other auxiliary tables (such as lookup tables) for your asset types.

     Note:

     Only five fields are provided for table names. If you have to enter more than five table names, complete this procedure through step 6 for the first five tables, then repeat steps 3 through 6 for the remaining tables.

6. Click Mirror.

   If initialization is successful, WebCenter Sites displays a confirmation message (otherwise, an error message opens).

   Based on the sites that you selected in step 4, the corresponding rows from the Publication, SitePlanTree, and AssetType tables are copied to the destination.

   If you specified auxiliary tables in step 5, all rows in those tables are copied to the destination.

1. In the General Admin tree on the source system, expand the Admin node, expand the Sites node, and double-click the site whose data you want to publish to the destination.
2. In Publish Destinations field (near the bottom of the form), click Mirror site configuration for destination.

   The Mirror Site Configuration form opens.

   Figure 16-4 Mirror Site Configuration Form

   
   Description of "Figure 16-4 Mirror Site Configuration Form"
3. Select the data you wish to mirror to the destination:

   Note:

   Which data you choose to mirror typically varies with the purpose of the destination system:

   • If the destination system is strictly for delivery, it makes sense to mirror only asset types.

   • When content management functions are to be supported, mirror the remaining data as well.

   • Asset Types: Select the asset types to make available on the destination.

     If your asset types have subtypes and categories, choose the appropriate options from the list in the Asset Types section and select the corresponding check boxes. For example, the AssocNamed table contains information about associations for asset types. The table is mirrored only if you select Asset associations for selected asset types and then the relevant asset types.

   • Start Menu Items: Select any start menu items that you or the developers designed for your content providers to use.

   • Workflow Processes: If there are workflow processes for your asset types, select these processes and the appropriate workflow items.

   • Workflow Groups: Select any workflow groups that you or the developers designed for your content providers to use.

   • Tree Tabs: Select the tree tabs to make available on the destination.

   • Saved Searches: Select any saved searches that you or the developers designed for your content providers to use.

   • Roles: Select the roles that must exist on the destination.

4. Click Mirror.

   Based on which asset type configuration options you selected in step 3, appropriate rows from the AssocNamed, AssocNamed_Subtypes, and Category tables are copied to the destination:

   • If you selected Start Menu Items or Saved Searches, appropriate rows from the tables that implement those features are copied to the destination.

   • Based on the workflow configuration options you selected in step 3, appropriate rows from the workflow tables are copied to the destination.

5. Repeat steps 1 through 4 for each site whose assets you want to publish to the destination.

You can test your publishing process by using all publishable assets or a smaller collection. To publish assets to a test environment, you must first approve the assets you want to publish. The following topics provide instructions for approving and publishing assets:

• Approving Assets

• Publishing the Assets

1. Open the Property Management Tool, in the Admin interface, on the final destination system. (For instructions on accessing the Property Management Tool, see Properties in the Publish Category in the Property Files Reference for Oracle WebCenter Sites.)
2. In the Name field, enter xcelerate.publishinvalidate.
3. Click Search.
4. In the Properties section of the form, select the name of the property.
5. Set the value of this property to false.
6. Click Save.

1. Open the Publish Console (in the Admin interface, click Publishing in the menu bar).

   The Publish Console opens with the Active tab at the front.

   Figure 16-6 Publish Console

   
   Description of "Figure 16-6 Publish Console"

   There are some actions to note on this screen:

   • The circling green arrows on the Active tab indicate that at least one session is in progress. The number in parenthesis indicates the number of sessions in progress.

   • Each destination shown in the Destination column is an active link. Click the destination to open its Publish Status form.

   • Select the View Log check box to view the log as it is being created.

   • Click the red button to cancel the session.

2. To monitor a session, stay in the Active tab and select the destination where the session is running.

   The Publishing Status form opens.

   Figure 16-7 Publishing Status

   
   Description of "Figure 16-7 Publishing Status"

   Notice the five status bars, one for each publishing stage. The status bars are interactive.

   To view the percent completion of a stage, hold your cursor over the stage's status bar. As you hover, another tooltip opens showing the current asset type being processed. If you continue to hover, you will see the tooltip updating in real-time, always displaying the publishing system's last action.

   While a session is running, you can also view its log, click View Log to do so. Click Download Log to download the log for viewing once complete.

   The publishing jobs per each target of the multi-target publish can complete in different orders because they are independently run on each target during the transport phase. For example, CacheFluster for target 1 might complete before Unpacker for target 2.

Ongoing publishing sessions can be canceled (and restarted) by any user with publishing rights. When a session is canceled, session information is moved from the Active tab to the History tab. Here, the session can be rerun, but only if at least the second publishing stage was completed successfully before the cancellation and the session is the most recently canceled.

For instructions about canceling a publishing session, see the following topics:

• Canceling a Publishing Session from the Publish Console

• Canceling a Publishing Session from the Publishing Status Form

1. Open the Publish Console (in the Admin interface, click Publishing on the menu bar).

   The Publish Console opens with the Active tab at the front. The Active tab lists publishing sessions currently in progress.

2. Download the log file for an active session or a past session:

   • Active tab: Select a destination name, and click Download Log.

   • History tab: Select a destination name, click View log and select Download Log.

     The Publishing Status form opens.

3. When the session is complete, click Download Log and follow the prompts.

   The log file is in text format and can be opened in any text editor.

1. Open the Publish Console (in the Admin interface, click Publishing on the menu bar).

   The Publish Console opens with the Active tab at the front.

2. Select the History tab.

   All available logs are displayed.

   Figure 16-13 History Tab on Publish Console Form

   
   Description of "Figure 16-13 History Tab on Publish Console Form"
3. Select the box next to each log or logs you want to delete.
4. Click Delete.

   The selected logs are deleted.

   Note:

   As data is in FW_PUBDATASTORE is stored using Large Binary Objects it may be necessary have the DBA manually clean up the Large Binary Data after performing this operation.