Creation of Dynamic Publishing Destination in Fatwire

Posted: January 20, 2012 in Fatwire
Tags: , , , , , , , , , ,

Dynamic Publishing is the process of publishing the content (assets) to some other machine/destination. This Dynamic Publishing is of two types.

1. Mirror to Server : Mirror to Server is the method used to copy database rows to remote dynamic server

2. Real time Publishing : Real time Publishing is the method used to copy assets to remote dynamic server.

Out of these both, Mirror to Server is the one which is used mostly. Mirror to Server is built with the Content Server Mirror API to copy approved assets from the Content Server database on one system to the Content Server database on another system.


The following steps are involved in the creation of a DYNAMIC PUBLISHING DESTINATION:

  • Login to the Advanced user interface.
  • Go to the admin tab of the tree.
  • Click on ADD NEW. The following screen appears:

  • In the “DELIVERY TYPE” drop down, select “MIRROR TO SERVER: Copy database rows to remote dynamic server”.
  • Enter a name for the publishing destination in NAME field
  • In the “DESTINATION ADDRESS” field, enter the name of the server, its port, followed by “/cs/”. For example, if  is the page which you use for logging into the advanced UI (URL of Remote Server), then the Destination address would look like this http://samplenodecom:8080/cs/
  • Enter the user name in “REMOTE USER” field.
  • Enter the password in “REMOTE PASSWORD” field.
  • Select the roles which approve the assets for publishing to this location.
  • Select the roles which can publish to this destination.
  • Select the sites for which this destination will be available.
  • Click on ADD NEW DESTINATION button in the bottom.

In this way, the Dynamic Publishing destination can be created.

Once the dynamic destination has been created, we need to check whether the destination is working properly or not. This can be known by observing the GREEN BULB image seen as shown in the image below. If a RED BULB image is shown, then there is some problem in connecting to the destination, like network issues, remote server might be down, licensing issues of the remote server for fatwire, VPN connectivity issues, etc. If any of the above issues arise, you need to consult the Fatwire / System Administrator of your company.

In this way, the Mirror to Server destination needs to be created and configured.

The rest of the APPROVAL, STATUS, PUBLISHING process is same as Static Publishing.

  1. srangach says:

    Hi KK,

    I have a question here. say an environment A has some assets and environment B has lot of assets. Now when i try to publish the Assets of env B to A . It has lot associated assets like Attributes,Content Def,Parent Def’s..etc. That time some how Mirror to Server stops by throwing an error at certain stages @ database level and what happens is I lost some of the exisiting Assets in my Env A.Thats a strange Behaviour. so for this purpose “Real TIme Publishing” gave hand to me… just a situation i faced i am sharing here….

  2. srangach says:

    i think Real time publishing is better for an unbalanced environment (meaning missing assets from env to env or any defintions or any other..etc) and Mirror to server is very helpful when its a kind of environment where it exactly depends or mirrors the other…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s