Creating a syndication relationship

To set up syndication between libraries on two IBM® Web Content Manager applications, establish a relationship between a syndicator on the server containing the data to be replicated and a subscriber on the server that receives the replicated data.

Before you begin

Important:
  • If you intend to syndicate a library that contains more than 10000 items, update the maximum Java heap size used by the portal application server on the subscriber machine:
    1. In the administrative console for IBM WebSphere® Application Server, navigate to the Java Virtual Machine settings.
      Standalone 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.
  • You can only syndicate between servers running the same version. You cannot syndicate between versions. For example:
    • you can syndicate between versions 7.0.0.0 and 7.0.0.1
    • you cannot syndicate between versions 6.1.5 and 7.0.0.0
  • Ensure that you have at least as much swap space allocated on the subscriber machine as you have physical memory.
  • 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.
  • Information about a 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, you must manually make the same changes to any subscriber libraries if you want the same settings on all your syndicated libraries.
  • If content from one library (Library A) uses an item from another library (Library B), you must include both libraries in the syndicator to ensure that all items are syndicated successfully.
  • If you only include Library A in the syndicator, any items in Library A that reference items in Library B are not syndicated, and syndication errors are generated.
  • If you add a new library to a syndicator after the initial syndication you must click Update 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 syndicating "All items", then both syndication relationships must be syndicating "All items".

Procedure

To set up a syndication relationship, complete the following steps:

  1. Ensure both the subscriber and syndicator are running and that they can access each other over a network.
  2. On your subscriber machine, log in to IBM WebSphere Portal.
  3. Go to Administration > Access > Credential Vault and create a credential vault slot to allow you to access the syndicator
  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
  7. Enter a name for the syndicator item. This name is used as the name of the syndicator item created on the syndicator server, so enter a name that helps identify the syndication relationship you are creating.
  8. Enter a name for the subscriber item. This name is used as the name of the subscriber item created on the subscriber server, so enter a name that helps identify the syndication relationship you are creating.
  9. Select the credential vault slot you created previously.
  10. Click Next
  11. Select the libraries you want to subscribe to.
    1. Click Add Libraries to select a library to syndicate and the syndication type:
      Live items:
      Live item syndication is mostly used when syndicating 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:
      The advantage of using "Live and projects" syndication is to gradually syndicate projects to a staging or delivery server rather that waiting to syndicate all the items in a project after they all 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 syndicating 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
    2. Select libraries from the current list and click Remove Libraries to remove a library from the list of syndicated libraries.
  12. Click Finish.
  13. To begin syndication, click either Update Subscriber or Rebuild Subscriber button.