Creating a syndication relationship from the command line
You can set up syndication relationships by using the Administration Portlets or the command line. To set up a syndication relationship from the command line, use the XML configuration interface (XML access) and the ConfigEngine command to configure the subscriber.
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:
- In the WebSphere Integrated Solutions Console,
browse to the Java virtual machine settings.
- Stand-alone server:
- Clustered server:
- Update the value in the Maximum Heap Size field. A value of at least 1024 MB is recommended.
- Click OK, and then save your changes.
- In the WebSphere Integrated Solutions Console,
browse to the Java virtual machine settings.
About this task
What
can and cannot be syndicated:
- Changes to only the library name or description are syndicated. Changes to other library properties, such as user access to a library, 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".