Posts Tagged ‘of’


NOTE: ALL THE CUSTOMIZATIONS I’M MENTIONING HERE ARE TESTED AND WORKING.
CONFIGURE THE SEARCH RESULTS SCREEN OF DASH INTERFACE IN FATWIRE:

Case 2: Modify the columns of the search results screen in the Dash Interface.

Explanation: By default, in the search results screen of the Dash UI, the following columns/fields are available: Name, Type, Modified, Locale, Start Date, End Date. In this article, we will see where and how to modify these fields.

Solution: For this customization to take place, we need to do modifications in the UIADMIN.PROPERTIES file.

The file is available in the following location:

C:\FatWire\JSK\7.5Patch5\App_Server\apache-tomcat-6.0.18\webapps\cs\WEB-INF\classes

Open the UIADMIN.PROPERTIES file.

We have a property in that file called “searchtableattrcols”, which specifies the columns that should be displayed in the UI.

The property is set by default as follows:

searchtableattrcols=AssetType,name,updateddate,locale,startdate,enddate

The search results screen of the Dash UI displays the following fields:

We need to change the above value to what ever we want.

Lets remove the Start Date and End Date values from the property, and see what happens. The property looks as follows:

searchtableattrcols=AssetType,name,updateddate,locale

Save the UIADMIN.PROPERTIES file.

Check the Dash UI’s Search results screen for the changes to reflect.

In the search results, we can find that the Start Date, End Date are omitted.

That’s it…! The customization has been done.

Stay tuned for more customizations in my upcoming articles.


Its always interesting to customize the existing out-of-box features given by the software vendor. Apart from being interesting, we might ght some times to customize the interface according to the clients requirements. We will discuss some of the customizations to the user interface, especially the DASH interface of Fatwire, in few of my upcoming articles.

NOTE: ALL THE CUSTOMIZATIONS I’M MENTIONING HERE ARE TESTED AND WORKING.
CONFIGURE THE SEARCH RESULTS SCREEN OF DASH INTERFACE IN FATWIRE:

Case 1: Change the SEARCH RESULTS COUNT of the search feature in the Dash Interface.

Explanation:  This customization is related to the search feature of the UI. We need to change the number of assets returned through search. For example, I would like to limit the search results to a 100 assets, instead of displaying the entire results. Hence, we need to find the properties file, in which we need to do modifications.

Solution: For this customization to take place, we need to do modifications in the UIADMIN.PROPERTIES file.

The file is available in the following location:

C:\FatWire\JSK\7.5Patch5\App_Server\apache-tomcat-6.0.18\webapps\cs\WEB-INF\classes

Open the UIADMIN.PROPERTIES file.

We have a property in that file called “searchresultscount”, which specifies the maximum assets that should be returned in the results, through the search performed by the user.

The default value of searchresultscount is 500 ,i.e., the following property is set by default:

searchresultscount=500

When searched for an assets of a particular asset type, the search results screen of the Dash UI displayed the following:

We need to change the above value to what ever we want. For example, if I want the results to be limited by 100, then I would set like this:

searchresultscount=100

Save the UIADMIN.PROPERTIES file.

Check the Dash UI’s Search results screen for the changes to reflect.

When searched for the same assets of the asset type searched above in the Dash Interface, and we can observe that the search results are limited. Verify the screen below:

That’s it…!

Stay tuned for more customizations in my upcoming articles.


Types of CS Administrators in Fatwire:

We use the term “Admin” / “Administrator” frequently. But, there are different types of Administrators defined by the Content Server in Fatwire. We will now see the different types of Administrators in Fatwire:

  1. General Administrator:  He is the normal Administrator. He is responsible for managing all systems in the Content Server environment and has full and unrestricted access to each system’s interfaces. He is also responsible for the creation of other users, creation of ACLs for them, and managing them.
  2. Site Administrator: He is the admin for a particular Site / Sites. He has access only to the site he is granted, and this user is generally created and manged by the General Administrator.
  3. Workflow Administrator: He is the one, who creates workflow processes. He creates the workflow processes, and the rest of the users participate in the workflow.

This is an overview of Administrators in Fatwire. Basing on the requirements, the above said roles will be created.


In this topic, we are going to discuss the CREATION OF USERS IN FATWIRE. To create a user in Fatwire, you need to login with ADMIN Credentials. Users can be created in Fatwire using ADVANCED UI, and the WEM UI. We are going to learn how to create the users in ADVANCED UI of FATWIRE.

CREATION OF USERS IN FATWIRE:

1. Login to the ADVANCED  UI with Admin credentials.

2. Go to the ADMIN tab of the Advanced UI.

3. Expand “CONTENT SERVER MANAGEMENT TOOLS“. After expanding this, you will be able to see SITE, ELEMENT, ACLs, USER, etc.

4. Double click on USER. The following screen appears. In this screen, as shown below, we can MODIFY USERS, ADD USERS, DELETE USERS, MODIFY USER ATTRIBUTES.

5. Enter a name for the user in the ENTER USER NAME field. This name will be the login username for the new user.

6. Click on ADD USER radio button.

7. Click on the OK button. The following screen appears.

8. Assign the ACCESS PRIVILEGES for the user, as required.

9. Enter the PASSWORD, and re enter the same in RE-ENTER PASSWORD field.

10. Click on the ADD button.

That’s it.. A NEW USER IS CREATED IN FATWIRE.


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.


It’s common for a software product to undergo changes, made by its R & D team, and to have newer versions. Basing on the changes that have implemented, the releases might be MINOR or MAJOR. The same applies for Alfresco as well. Lets discuss the upgrade process of Alfresco (Both Minor and Major upgrades).

UPGRADING TO A MINOR RELEASE:

This type of upgrade will be between the minor releases such as 3.0 to 3.0.1, 3.3 to 3.4, etc. As there will be no new features, except some small patches and minor UI changes, we can do the upgrade by simply replacing the Web Application (WAR) file.

The WAR file can be downloaded, and replaced with the existing WAR files under <install_folder>\tomcat\webapps.

The following steps can be followed for upgrading the alfresco with minor release:

1. Download the latest release of Alfresco WAR file from the Alfresco website.

2. Stop the alfresco instance. (TOMCAT and MySQL).

3. Backup the data, and the customization files.

4. Delete the Alfresco folder in <install_folder>\tomcat\webapps.

5. Replace the existing Alfresco.war file in the above said location with the recently downloaded WAR file.

6. Restore the customizations (If any).

7. Start Alfresco

The Above said procedures will upgrade Alfresco to a new minor release.

UPGRADING TO A MAJOR RELEASE:

This type of upgrade will be between the Major releases such as 2.x to 3.x, 3.x to 4.x, etc. An Alfresco’s major release contains new features, performance enhancements, and bug fixes.

The following steps can be followed for upgrading the alfresco with minor release:

1. Download the complete Alfresco package and the Tomcat bundle for the Windows operating system.

2. Stop Alfresco.

3. Backup the data, and the customization files.

4. Perform a new installation in a different folder.

5. Copy the older Alfresco file content folder to the newer installation

(Copy C:\alfresco_old_version\alf_data folder to C:\alfresco_new_version\alf_data).

6. Create a new database table, and restore the relational database content from the older database.

7. Update the Alfresco configuration file (alfresco-global.properties) in the new installation, to point to this new database.

8. Restore the customization files in the new installation.

9. Start Alfresco in the new installation.

The Above said procedures will upgrade Alfresco to a new Major release. Test thoroughly to verify whether your old configurations are working fine with the new release or not.

More information regarding the upgrade process can be found here in the alfresco site.