Verifying the installation

Follow these procedures to test and verify the critical parts of the new Content Manager installation.

About this task

In general the following should never result in an error and cause no harm on a production system. Testing more complex setups, such as the batch servers is out-of-scope.

Procedure

  1. Log in into the Content Manager Web client as an existing user.
    For example, go to http://servername/InfoShareAuthor and login using an existing login name and password, or the admin name and password.
  2. Test the inbox by selecting the Inbox tab then select one of the inbox tabs in the left pane.
    Test is successful if the inbox is displayed in the right pane in a table format.
  3. Create a folder in the repository:
    1. Select the Repository tab.
    2. Create a folder by clicking the New Folder icon in the upper left pane.
    3. Enter a name.
    4. Click Ok.

    Test is successful if the folder is created (shown in the left pane). Remove the folder after verifying using the Delete Folder button in the upper left pane.

  4. Test publishing; if a publication is not available, skip this test.
    1. Select the Repository tab.
    2. Locate a publication (traverse the left pane) and select the publication (in the right pane).
    3. Select an output type in the bottom pane.
    4. Click Publish.
      A confirmation window is displayed.
    5. Click OK in the confirmation window.
      The publication output status (bottom right pane of the search window) changes to Pending.
    Test is successful if the output status changes to Draft; refresh the view to confirm that the status changes to Draft.
  5. Execute a full text search:
    1. Select the Search tab.
    2. Enter a term in the Search term field.
      Be sure to enter a word that you know exists in your topics. For example, enter the search word: the.
    3. Click Search.
    Test is successful if search results are displayed in the right pane.
  6. Verify web services, synchronization, and network availability by starting the Client Tools such as Publication Manager, Condition Manager or Authoring Bridge.

    Test is successful if you can view the repository through the client tools and can view or preview a topic in the repository.

  7. Verify requested customizations to your system such as PDF stylesheets, extra metadata, or extra development for integration with other systems (such as SDL-TMS, PLMs, SingleSignOns).

    Ask your Content Manager administrator or documentation manager what customizations, if any, were requested.