Create a syndication relationship using the Administration Portlets

Before running syndication, ensure the subscriber has sufficient disc space to receive the data being syndicated from the syndicator. For example, if we are going to syndicate all libraries, we will need at least as much space on the subscriber as the database used by the syndicator.

Verify there is at least as much swap space allocated on the subscriber server as there is physical memory.
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.

First-time syndication to an existing library is not supported. If we attempt to syndicate a library to a subscriber that already has a library with the same name, an error results.

To syndicate a library containing more than 10000 items, update the maximum Java heap size used by the portal application server on the subscriber server:

1. In the WAS console, navigate 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 the changes.

Information about a 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 we change the name of a library or change user access to a library, these changes are not syndicated. The same settings on all the syndicated libraries, manually make the same changes to any subscriber libraries. If content from one library (Library A) uses an item from another library (Library B), include both libraries in the syndicator. Including both libraries ensures that all items are syndicated successfully. If we 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 we add a library to a syndicator after the initial syndication, click Rebuild to force the new library to be syndicated immediately. If we are creating a two-way syndication relationship, use a consistent syndication strategy. For example, if syndicating "All items", then both syndication relationships must be syndicating "All items".

Set up syndication relationship

1. Ensure both the subscriber and syndicator are running and they can access each other over a network.

2. On the subscriber server, log in to IBM WebSphere Portal and go to...
   Administration | Access | Credential Vault

   Create a shared credential vault slot to allow you access to the syndicator.

   This user ID and password must be exist on the syndicator server.

3. Go to...
   Administration | Portal Content | Subscribers | Subscribe Now

4. Enter the syndicator URL in the form of...
   http://Host:Port/WcmContextRoot
   For example:
   http://authoring:10039/wps/wcm

   When syndicating from a virtual portal:

   Use the URL context of a virtual portal:

   http://host:port/wps/wcm/url_context

   Use the hostname of a virtual portal:

   http://virtualhost:port/wps/wcm

5. Enter a name for the syndicator item.

   This name is used for the syndicator item created on the syndicator server. Enter a name that helps identify the syndication relationship we are creating. This name must be unique and cannot be the same as an existing syndicator name.

   To reuse syndicator names of previously deleted syndication relationships on a subscriber, delete the same relationship on the syndicator.

6. Enter a name for the subscriber item.

   This name is used for the subscriber item created on the subscriber server. Enter a name that helps identify the syndication relationship we are creating. This name must be unique and cannot be the same as an existing subscriber name.

7. Select the credential vault slot created previously.

8. Click Next

9. Select the libraries 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:

      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 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.

10. Click Finish.

11. To begin syndication, click either Update Subscriber or Rebuild Subscriber button.

Parent Work with syndicators and subscribers