We will first install SCS Target software on the web server machine and then apply the SP2 pack over it.
Figure 7.7 lists some of the prerequisites for installing SCS Target on the web server host:
Entity |
Comments |
---|---|
SCS Target installation owner |
On Windows machines, the user should:
|
Transfer user |
User name and password for a valid OS user on the SCS Target machine should be known |
Web Server |
The web server for application servers or web applications should be up and running |
Database |
If configured with SCS Target software, the database instance should be accessible User name and password for Database connectivity should be available DB system user name and password should be available for allowing Site Caching Services to create database/tablespaces. |
Hardware |
250 MB hard disk space, 128 MB RAM, and 133 MHz CPU Post installation, the website host should have adequate disk space for storing the published data. |
Others |
For supported combinations of Windows OS and RDBMS versions, please refer to Release Notes from Documentum. |
To begin, download the following SCS Target software installation files from the Documentum site:
Site_Caching_Services_5.2.5_windows_target.exe
Site_Caching_Services_5.2.5_SP2_all.zip
We will first install SCS Target 5.2.5 on the web server host and then upgrade it with service pack 2 (SP2).
Site_Caching_Services_5.2.5_windows_target.exe
and run the following executable: SCSTargetWinSetup.exe
Set up a DSN (Data Source Name) on the SCS Target machine, in the way we did when we created our first Docbase. Recall that the DSN can be created on a Windows machine by going to Programs | Administrative Tools | Data Sources (ODBC).
Remember that secure (HTTPS) communications can be about 30% slower than non-secure communications. If your network and the traffic between the Content Server host and the target machine is secure, you can select non-secure communication.
We are done with installation of SCS Target 5.2.5 on the web server host. The next task is to apply service pack 2 to it. As part of SCS Target configuration, Documentum modifies the agent.ini
file on SCS Target host at the following location:
<SCS Target Installation Directory>adminconfig<SCS Target port>
On Windows, a typical location would be: C:DocumentumSCSadminconfig2788
The following snippet is from the agent.ini
file that stores the database information for SCS Target that we just installed above:
target_database_connection=jdbc:odbc:SCS_TARGET_PUBLISHING_DSN database_user=sa database_user_pass=systempass JDBC_DRIVER=sun.jdbc.odbc.JdbcOdbcDriver database_name=WebCache_2788
We will now install SCS Target 5.2.5 SP2 on the web server host.
Site_Caching_Services_ 5.2.5_SP2_all.zip
on the web server host. This ZIP contains the webcache.jar
file. webcache.jar
file at the following location on the web server host:<SCS Target Installation Directory>productjrewinlibext
Example: A typical location on Windows could be: C:DocumentumSCSproductjrewinlibext
If the SP2 upgrade is not done correctly, the following error message is seen during publishing, if there is a mismatch in the versions of webcache.jar
on the Content Server host and the web server host (for SCS Source and Target):
ERROR: Failed to login to the target server. Network error retrieving target result
com.documentum.webcache.utils.d; Local class not compatible: stream
classdescserialVersionUID=1602290069170353386 local class
serialVersionUID=4590497449032455007
That's it! We have finished upgrading SCS Target to SP2. We are now ready to publish content and metadata from Documentum.
3.144.16.71