IBM WebSphere Portal 8.5: User assistance for administrators

Creating a syndication relationship by using the Administration Portlets

You can set up syndication by using the Administration Portlets or the command line.

Before you begin

Make sure that you have the appropriate configuration setup before you enable syndication.
Disk space
Before you use syndication, you must ensure that your subscriber has sufficient memory to receive the data that is syndicated from the syndicator. For example, if you are going to syndicate all libraries, then you need at least as much space on your subscriber as the database used by your syndicator.
Swap space
Ensure that you have at least as much swap space allocated on the subscriber server as you have physical memory.
Cross version syndication
Cross-version syndication is supported between the following releases. Syndication from a newer release to an older release is not supported:
  • WebSphere® Portal version 7.0.0.2 with CF26 or higher.
  • WebSphere Portal 8.0.0.1 with CF09 or higher.
  • WebSphere Portal 8.5 or higher.
Library already exists on the subscriber
First-time syndication to an existing library is not supported. If you attempt to syndicate a library to a subscriber that already has a library with the same name, an error results.
Large library with more that 10000 items
To syndicate a library that contains more than 10000 items, update the maximum Java heap size that is used by the portal application server on the subscriber server:
  1. In the WebSphere Integrated Solutions Console, browse to the Java virtual machine settings.
    Stand-alone server:
    Servers > Server Types > WebSphere application servers > WebSphere_Portal > Java and Process Management > Process definition > Java Virtual Machine
    Clustered server:
    System administration > Deployment manager > Java and Process Management > Process Definition > Java Virtual Machine
  2. Update the value in the Maximum Heap Size field. A value of at least 1024 MB is recommended.
  3. Click OK, and then save your changes.

About this task

To set up syndication between web content libraries on two IBM® Web Content Manager applications, establish a relationship between a syndicator and a subscriber. The syndicating server contains the data to be replicated, and the subscribing server receives the replicated data.
What can and cannot be syndicated:
  • Information about a web content library is only syndicated the first time syndication occurs and not on subsequent updates and rebuilds. If a library is renamed or library user access is changed, this information is not syndicated to the Subscriber.
  • If you change the name of a library or change user access to a library, these changes are not syndicated. If you want the same settings on all your syndicated libraries, you must manually make the same changes to any subscriber libraries.
  • If content from one library (Library A) uses an item from another library (Library B), you must include both libraries in the syndicator. Including both libraries ensures that all items are syndicated successfully.
  • If you include only Library A in the syndicator, any items in Library A that reference items in Library B are not syndicated. Syndication errors are also generated.
  • If you add a library to a syndicator after the initial syndication, you must click Rebuild to force the new library to be syndicated immediately.
  • If you are creating a two-way syndication relationship, you must use a consistent syndication strategy. For example, if you syndicate "All items", then both syndication relationships must be syndicating "All items".

Procedure

  1. Ensure both the subscriber and syndicator are running and that they can access each other over a network.
  2. On your subscriber server, log in to IBM WebSphere Portal.
  3. Go to Administration > Access > Credential Vault and create a shared credential vault slot. The user assigned access to the credential vault must exist on the subscriber and must have access to the WCM REST SERVICE virtual resource.
  4. Go to Administration > Portal Content > Subscribers.
  5. Click Subscribe Now.
  6. Enter the syndicator URL in the form of http://HostName:HostPort/WcmContextRoot. For example: http://authoring:10039/wps/wcm
    Note:
    When you syndicate from a virtual portal:
    Using the URL context of a virtual portal:
    http://HostName:HostPort/wps/wcm/url_context
    Using the hostname of a virtual portal:
    http://VirtualHostName:HostPort/wps/wcm
  7. Enter a name for the syndicator item. This name is used for the syndicator item that is created on the syndicator server. Enter a name that helps identify the syndication relationship that you are creating. This name must be unique and cannot be the same as an existing syndicator name.
    Note: To reuse syndicator names of previously deleted syndication relationships on a subscriber, you must also delete the same relationship on the syndicator.
  8. Enter a name for the subscriber item. This name is used for the subscriber item that is created on the subscriber server. Enter a name that helps identify the syndication relationship that you are creating. This name must be unique and cannot be the same as an existing subscriber name.
  9. Select the credential vault slot that you created previously.
  10. Click Next
    Cross-version syndication: If you syndicate to a server where CF3 for IBM WebSphere Portal is not installed, steps 11 - 12 are skipped.
  11. This information applies to CF05Select a syndication schedule mode:
    • Configured: This option uses the mode that is configured in the WCM WCMConfigService service.
    • Automatic: Syndication is scheduled automatically based on the configured syndication interval.
    • Manual: Syndication occurs only when requested by using the administration portlet.
  12. Click Next
  13. Select the libraries that you want to subscribe to and the syndication type.
    Live items:
    Live item syndication is mostly used when you syndicate to a staging or delivery server. The following items are syndicated:
    • Published
    • Expired
    Draft items, projects, and items in a project are not syndicated.
    Live and projects:
    Use "Live and projects" syndication to gradually syndicate projects to a staging or delivery server, rather than waiting until all items in a project achieve a published state. The following items are syndicated:
    • Published
    • Expired
    • Projects
    • Draft items in a project
    Draft items outside of projects are not syndicated.
    All items:
    All item syndication is mostly used when you syndicate between servers within an authoring environment. The following items are syndicated:
    • Published
    • Expired
    • Projects
    • Draft items in a project
    • Other draft items
    • Versions
    • Deleted items
  14. Click Finish.
  15. To begin syndication, click Update Subscriber.
Parent topic: How to manage syndicators and subscribers
Library | Support | Terms of use |

Thursday, May 7, 2015 12:23am EST

Copyright IBM Corporation 2000, 2014.