Posts Tagged ‘Dynamic’


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.

CREATION OF DYNAMIC PUBLISH DESTINATION:

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.
  • Expand PUBLISHING -> DESTINATIONS.
  • 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  http://samplenode.com:8080/cs/Xcelerate/LoginPage.html  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.


In our previous posts, we have seen how to work with Static Publishing. In this post, we will see how to work with Dynamic Publishing.

DYNAMIC PUBLISHING, also known as MIRROR TO SERVER PUBLISHING method, is one of the important Publishing methodologies of Fatwire. It 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.

HOW IT WORKS:

The following image explains how the Mirror to Server publishing works in simple.

To be more precise,

1. When the Dynamic Publishing is done, the Local content server (on which the main database, file structure, etc are there) mirrors,i.e, copies the entire file structure to the remote server (the machine which hosts the site).

2. The user requests a page.

3. The request will be received by the server (i.e, the mirrored remote CS Server).

4. The CS dynamically generates the pagelets and pages, and delivers it to the webserver.

5. The webserver then delivers it to the end user who has requested the page.