Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Note: This SAS Note currently replaces "Reconfiguring the SAS Content Server to Share the Database Used by SAS Shared Services" in the SAS^® 9.2 Intelligence Platform: Web Application Administration Guide, Third Edition.

Beginning with the third maintenance release for SAS^® 9.2, SAS Content Server supports database persistence. By default, the SAS Content Server uses the file system for persistence. Generally, you do not need to change this setup. However, in some environments, there might be a compelling need to use a back-end database. In such cases, you can reconfigure the SAS Content Server to share the database that is used by SAS Shared Services.

By default, SAS Shared Services uses the SAS^® Table Server. However, you can configure SAS Shared Services to use a different database such as the SAS Threaded Kernel Table Server (TKTS), Oracle, MySQL, Postgres, IBM DB/2, or Microsoft SQL Server.

To migrate the contents of the current SAS Content Server repository to a database repository, download either the JCRCopyRepository.bat or the JCRCopyRepository.sh script file from the Downloads tab. Then place the script file in the SAS-configuration-directory/Web/Utilities directory, and customize the file for your environment. After you customize and save the file, follow the steps below to reconfigure the SAS Content Server so that it shares and uses the same database that is used by SAS Shared Services:

1. Stop the Web application server. Typically, this server is named SASSERVER1 in the Web application server's configuration directory.
2. Rename the SAS Content Server repository from Repository to RepositoryFS.
• For Windows operating environments, use the following command:
  move C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\Repository C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\RepositoryFS
• For UNIX and z/OS operating environments, use the following command:
  mv SAS-configuration-directory/Lev1/AppData/SASContentServer/Repository SAS-configuration-directory/Lev1/AppData/SASContentServer/RepositoryFS
3. Next, create a new directory called Repository in the same location:
   • Under Windows, use the following command:
     mkdir C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\Repository
   • Under UNIX and z/OS, use the following command:
     mkdir SAS-configuration-directory/Lev1/AppData/SASContentServer/Repository
4. In the repository.xml file, identify the database that is used for SAS Shared Services. To do that, copy the repository.database-name.xml file from SAS-installation-directory/SASWebInfrastructurePlatform/9.2/Static/wars/sas.svcs.scs/WEB-INF/templates to the directory that you created in step 3. Then, rename repository.database-name.xml to repository.xml, as shown in the following commands that use the TKTS database as an example:
• Under Windows:
  copy C:\SASHOME\SASWebInfrastructurePlatform\9.2\Static\wars\sas.svcs.scs\WEB–INF\templates\repository.tkts.xml C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\Repository\repository.xml
• Under UNIX:
  cp /$SASHOME/SASWebInfrastructurePlatform/9.2/Static/wars/sas.svcs.scs/WEB–INF/templates/repository.tkts.xml SAS-configuration-directory/Lev1/AppData/SASContentServer/Repository/repository.xml

5. If your server is a Red Hat JBoss Web application server, follow these steps:

   1. Open the repository.xml file and search for the following parameter:
      <param name="url" value="sas/jdbc/SharedServices"/>
   2. Modify that parameter as follows:
      <param name="url" value="java:sas/jdbc/SharedServices"/>

      This value appears six times within the repository.xml file. You must modify all six instances of the parameter.

   Note: If a workspace.xml file exists in the SAS-configuration-directory/Lev1/AppData/SASContentServer/Repository/workspaces/default directory on the middle-tier server, it will contain two instances of the same parameter. You must also modify those two instances as well with the value <param name="url" value="java:sas/jdbc/SharedServices"/>.

6. Obtain the values for the database name, host, port, user ID, and password from the Web Application Server.
• On the JBoss Web application server, these values are located in the SharedServices–ds.xml file that resides in SAS-configuration-directory/Lev1/Web/Common/jboss.
• On the IBM WebSphere application server, the values are available via the WebSphere Administration Console. In the console, select Resources ► JDBC ► Data Sources ► Custom Properties.
• On the Oracle WebLogic application server, the values are available via the WebLogic Administration Console. Select SASDomain ► Services ► JDBC ► Data Sources ► SharedServices ► Configuration and click the Connection Pool tab. The values are available on this tab.

7. In the JCRCopyRepository script that you previously placed in SAS-configuration-directory/Web/Utilities, modify the value of the DRIVER= parameter, so that it indicates the path to the JDBC driver for the database. The syntax for the DRIVER= parameter is as follows:
   driver=path–to–the–jdbc–driver–JAR–file

The directory path should include the list of JAR files. The listed JAR files should be concatenated by semicolons (under Windows) or colons (under UNIX).

• Example of concatenated JAR files in the DRIVER= path under Windows:
  driver=SAS-configuration-directory\Lev1\Web\Applications\SASSharedServices9.2\JDBCDriver\icu4.jar; SAS-configuration-directory\Lev1\Web\Applications\SASSharedServices9.2\JDBCDriver\log4j.jar; . . .additional-JAR-paths. . .
• Example of concatenated JAR files in the DRIVER= path under UNIX and z/OS:
  driver=SAS-configuration-directory/Lev1/Web/Applications/SASSharedServices9.2/JDBCDriver/icu4.jar: SAS-configuration-directory/Lev1/Web/Applications/SASSharedServices9.2/JDBCDriver/log4j.jar: . . .additional-JAR-paths. . .
8. Specify the values for user ID and password (That you retrieved in the previous step) in the JCRCopyRepository script file, as follows:
• Under Windows:
  –Dscs.jndi.user=database-user-ID ^ –Dscs.jndi.pwd=password \
• Under UNIX:
  –Dscs.jndi.user=database-user-ID \ –Dscs.jndi.pwd=password \
9. In the same JCRCopyRepository script file, enter the values for the following parameters:
• Under Windows:
  –Dscs.jndi.jdbcUrl=jdbc-url ^ -Dscs.jndi.driver=jdbc-driver-class ^
• Under UNIX:
  –Dscs.jndi.jdbcUrl=jdbc-url \ -Dscs.jndi.driver=jdbc-driver-class \

The values that you specify for the JDBC URL and for the driver are determined by the type of database that is used in your environment. The following table lists the values for the different types of databases:

Parameters and values for the JDBC URL and the driver

Database	Parameters	Values
TKTS	-Dscs.jndi.jdbcUrl	jdbc:sastkts://host:2171?constring=(DSN=SharedServices)
TKTS	-Dscs.jndi.driver	com.sas.tkts.TKTSDriver
Oracle	-Dscs.jndi.jdbcUrl	For Oracle: jdbc:oracle:think:@host:1521:orcl For Oracle XE: jdbc:oracle:think:@host:1521:xe
Oracle	-Dscs.jndi.driver	oracle.jdbc.driver.OracleDriver
Postgres	-Dscs.jndi.jdbcUrl	jdbc:postgresql://host:5432/SharedServices
Postgres	-Dscs.jndi.driver	org.postgresql.Driver
DB2	-Dscs.jndi.jdbcUrl	jdbc:db2//host:50000/database
DB2	-Dscs.jndi.driver	com.ibm.db2.jcc.DB2Driver
MSSQL	-Dscs.jndi.jdbcUrl	jdbc:sqlserver://host1433;DataBaseName=SharedServices;SelectMethod=cursor
MSSQL	-Dscs.jndi.driver	com.microsoft.sqlserver.jdbc.SQLServerDriver
MySql	-Dscs.jndi.jdbcUrl	jdbc:mysql://host:3306/SharedServices
MySql	-Dscs.jndi.driver	com.mysql.jdbc.Driver

10. In the command window, navigate to the SAS-configuration-directory/Web/Utilities directory.

11. Run the JCRCopyRepository script command by providing the complete directory path of the old and new repository directories, as follows:

    • Under Windows:
      JCRCopyRepository.bat C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\RepositoryFS C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\Repository
    • Under UNIX and z/OS:
      /JCRCopyRepository.sh SAS-configuration-directory/Lev1/AppData/SASContentServer/RepositoryFS SAS-configuration-directory/Lev1/AppData/SASContentServer/Repository
12. To enable all of the changes you made, restart the Web application server. As mentioned previously, that server typically is named SASSERVER1.

Operating System and Release Information

To migrate the contents of the current WebDAV repository to the database-based repository, use the JCRCopyRepository.bat or the JCRCopyRepository.sh files.

JCRCopyRepository.zip