Transcription

3 Table of Contents Prerequisite Steps... 1 Database Migration Instructions for the WebSphere Application Server... 1 Step 1: Extract the Web Infrastructure Platform and Shared Services data from SAS Table Server Step 2. Create the new target database Step 3. Populate the database with the tables that are needed for the Web Infrastructure Platform and Shared Services Step 4. Update the Web Infrastructure Platform and Shared Services data source that is defined in WebSphere Step 5. Update the configuration properties for the Web Infrastructure Platform and Shared Services Step 6. Migrate the Web Infrastructure Platform and Shared Services from SAS Table Server to the new database Step 7. Update the workflow to use the proper dialect Step 8. Populate the database with the tables that are needed for the SAS Content Server Step 9. Configure the SAS Content Server to use the new database as its repository Step 10. Verify that the new database is the new back-end data store Database Migration Instructions for the WebLogic Application Server Step 1: Extract the Web Infrastructure Platform and Shared Services data from SAS Table Server Step 2. Create the new target database Step 3. Populate the database with the tables that are needed for the Web Infrastructure Platform and Shared Services Step 4. Update the Web Infrastructure Platform and Shared Services data source that is defined in WebLogic Step 5. Update the configuration properties for the Web Infrastructure Platform and Shared Services Step 6. Migrate the Web Infrastructure Platform and Shared Services from SAS Table Server to the new database Step 7. Update the workflow to use the proper dialect Step 8. Populate the database with the tables that are needed for the SAS Content Server Step 9. Configure the SAS Content Server to use the new database as its repository Step 10. Verify that the new database is the new back-end data store Database Migration Instructions for the JBoss Application Server Step 1. Extract the Web Infrastructure Platform and Shared Services data from SAS Table Server Step 2. Create the new target database Step 3. Populate the database with the tables that are needed for the Web Infrastructure Platform and Shared Services Step 4. Update the Web Infrastructure Platform and Shared Services data source that is defined in JBoss Step 5. Update the configuration properties for the Web Infrastructure Platform and Shared Services i

4 Step 6. Migrate the Web Infrastructure Platform and Shared Services from SAS Table Server to the new database Step 7. Update the workflow to use the proper dialect Step 8. Populate the database with the tables that are needed for the SAS Content Server Step 9. Configure the SAS Content Server to use the new database as its repository Step 10. Verify that the new database is the new back-end data store Appendix ii

5 This document provides instructions for updating an existing deployment of the third maintenance release for SAS 9.2 (TS2M3) that is configured to use SAS Table Server. These instructions explain how to migrate from SAS Table Server to a SQL Server database for use with the SAS Web Infrastructure Platform, SAS Shared Services, and the SAS Content Server. Prerequisite Steps Before you attempt the migration steps that are provided in this document, complete the following tasks: 1. Download the SAS WIP Database Importer (ftp://ftp.sas.com/techsup/download/blind/dbimporter92m3.zip). 2. Install a Java 6 Java Runtime Environment (JRE). 3. Add the JAVA_HOME environment variable to your system environment properties and set it to the value of the installation home directory of the Java 6 JRE. 4. Download Apache Ant or later. In your command window or in your system s environment properties, set the ANT_HOME environment variable to the value of its installation home directory. Note: Apache Ant is included in the download for the SAS WIP Database Importer that is mentioned above in Step Download the SQL Server Java Database Connectivity (JDBC) driver Java Archive (JAR) file and add it to the jars/sqlserver/ directory that is defined in the build.properties file within the download for the SAS WIP Database Importer. Database Migration Instructions for the WebSphere Application Server Step 1: Extract the Web Infrastructure Platform and Shared Services data from SAS Table Server. Extract the data that is related to the Web Infrastructure Platform and Shared Services from SAS Table Server. To do this, use the SAS Migration Utility and package the data in a ZIP file. You use this file later to load the data into the new database. 1. Download the SAS Migration Utility (support.sas.com/demosdownloads/setupcat.jsp?cat=sas+migration+utility) and save it to a folder on your file system, such as C:\SMU. 2. Copy the contents of the smu.properties file that is located in the Appendix of this document and save it to a file on your system. 3. In the smu.properties file, update the values for the host name, port number, file path, user name, and password to match your environment. 4. Create the folder C:\SMU_packages on your file system. This is the location where the migration package will be created. The folder value should match the value for the SMU.Output.Dir property from the smu.properties file. 1

6 5. From the command prompt, change to the directory where the downloaded SAS Migration Utility is stored. 6. Submit the following command to create the migration package: smu92_32 -properties "path-to-your-smu.properties-file" -only biservmid Here is an example: smu92_32 -properties "C:\smu.properties" -only biservmid 7. Go to the C:\SMU_packages\your-environment\biservmid directory and locate the WIP_database.zip file, which contains the data from SAS Table Server. Step 2. Create the new target database. Install and configure the new target database if you do not already have one running. If needed, consult the database administrator at your site for assistance. Step 3. Populate the database with the tables that are needed for the Web Infrastructure Platform and Shared Services. Create the Web Infrastructure Platform and Shared Services tables in SQL Server. 1. Open the database_sqlserver.properties file from the SAS WIP Database Importer that you previously downloaded. Update the values for the following properties to match the values for your environment: database.host database.port database.name database.user.id database.user.password database.schema.pattern Note: The SQL Server database schema is the uppercased value of the log on ID (for example, ${DATABASE.USER.ID}). 2. Open the build.properties file from the SAS WIP Database Importer. Remove the comment delimiters from the following line: database.type=sqlserver 3. Update the values for the following properties to match the values for your environment: a. database.type specifies the type of the target database (for example, database.type=sqlserver). 2 b. sql.scripts.data.dir specifies the absolute path to the data directory in the SASHOME location, which contains the SQL scripts for the Web Infrastructure Platform that are used to create its database tables, load

7 its out-of-the-box data, and drop its database tables (for example, sql.scripts.data.dir=c:\\ Program Files\\SAS\\SASSharedServices\\9.2\\Config\\Deployment\\Data\\). c. database.zip.file specifies the absolute path to the v920m3 WIP_database.zip file from which records will be read and inserted into the target v920m3 database. The WIP_database.zip file is created by the SASSMU2 (for example, database.zip.file=c:\\public\\v920m3\dbimporter92m3 \\test\\sassmu2\\wip_database.zip). d. log4j.config.file specifies the Log4J configuration file which is used by the database importer for the Web Infrastructure Platform. Edit the log4j.properties file to specify the location of the log file (for example, log4j.config.file=file:///c:/public/v920m3/dbimporter92m3/ log4j.properties). e. java.maxmemory specifies the maximum amount of memory that can be used by the database importer for the Web Infrastructure Platform (Java application) (for example, java.maxmemory=2048m). 4. Open a command window and change to the SAS WIP Database Importer directory. Submit the createdatabasetables command to create the database tables for the Web Infrastructure Platform and Shared Services (for example, C:\DbImporter92m3> ant -f build.xml createdatabasetables). Step 4. Update the Web Infrastructure Platform and Shared Services data source that is defined in WebSphere. The initial installation created a data source named SharedServices that references SAS Table Server. This step redirects that reference to a new data source that relies on SQL Server. Before you create the JDBC provider (named SharedServices JDBC Provider) and the JDBC data source (named SharedServices), enter the value SQLServerJAASAlias in the JAAS - J2C Authentication Data Alias text box. This will contain the user ID and password that are used to authenticate the connection to the SharedServices data source. This alias will be referenced when you are creating the new JDBC data source SharedServices. 1. Log on to WebSphere (for example, 2. Select Security Secure administration, applications, and infrastructure Java Authentication and Authorization Service J2C authentication data link. 3. Enter the value SQLServerJAASAlias in the JAAS - J2C Authentication Data Alias text box. 4. On the JAAS - J2C Authentication Data New page, enter the following information for these required fields: Alias: SQLServerJAASAlias User ID: user-id-for-connection-to-the-database Password: password-for-connection-to-the-database Note: WebSphere stores this password using its own encoding mechanism. 3

10 a. data.dbms.type: sqlserver b. dbms.biservmid.host: SQLServer-host-name c. dbms.biservmid.jdbc.dir: directory-path-containing-the-sqlserver-jdbcdriver-jar d. dbms.biservmid.name: SQLServer-database-name e. dbms.biservmid.port: SQLServer-port-number f. dbms.biservmid.userid: SQLServer-userID g. dbms.biservmid.validation.query: select 1 from dual 7. Click OK to exit the dialog box, and then exit SAS Management Console. Step 6. Migrate the Web Infrastructure Platform and Shared Services from SAS Table Server to the new database. Migrate the data that was exported from SAS Table Server to the new database. 1. Open a command window and navigate to the directory for the SAS WIP Database Importer. 2. Submit the importdatabase command to create the Web Infrastructure Platform and Shared Services database tables (for example, C:\DbImporter92m3> ant -f build.xml importdatabase). Step 7. Update the workflow to use the proper dialect. Update the workflow in order to use the new database. 1. Open the sas.shared9.2.ear file. Within this EAR file, open the workflow.properties file, which resides in the \sas.workflow.war\web-inf\ directory. 2. Add a comment delimiter to the following line: workflow.hibernate.dialect=com.sas.workflow.engine.services.dao. TSFirebirdDialect Here is an example: workflow.hibernate.dialect=com.sas.workflow.engine.services.dao. TSFirebirdDialect 3. Remove the comment delimiter from the following line: workflow.hibernate.dialect=org.hibernate.dialect.sqlserverdialect Here is an example: workflow.hibernate.dialect=org.hibernate.dialect.sqlserverdialect 6 4. Redeploy the sas.shared9.2.ear file.

11 Step 8. Populate the database with the tables that are needed for the SAS Content Server. The scripts that were needed to create the tables for the SAS Content Server were executed by the createdatabasetables command in the previous steps. Step 9. Configure the SAS Content Server to use the new database as its repository. This section discusses the steps that are needed to migrate the stored SAS Content Server data from SAS Table Server to a SQL Server database. It also details the steps that are needed to configure the SAS Content Server for the new SQL Server database. In order to migrate the data, you need to convert the SAS Content Server from using the SAS Table Server to using the file system and then to using SQL Server. Revert to the file system after you have configured the SAS Content Server for SAS Table Server. 1. Stop WebSphere. 2. Back up the following directory: SAS-configuration-directory/Lev1/AppData/SASContentServer 3. Create a new directory as follows: SAS-configuration-directory/Lev1/AppData/SASContentServer/temp 4. Copy the repository.xml file that resides in the SASHOME/SASWebInfrastructurePlatform/9.2/ Static/wars/sas.svcs.scs/WEB INF/templates/ directory to the SAS-configurationdirectory/Lev1/AppData/SASContentServer/temp directory. 5. Change directory to SAS-configuration-directory/Lev1/Web/Utilities. Verify that your JCRCopyRepository.sh script has only one set of Java Naming and Directory Interface (JNDI) arguments for SAS Table Server. It should look similar to the following:!/bin/sh -p JCRCopyRepository.sh. `dirname $0`/../../level_env.sh LAUNCHERJAR=$SASVJR_HOME/eclipse/plugins/sas.launcher.jar UTILITIESDIR=$LEVEL_ROOT/Web/Utilities PICKLISTS=/sas/SASWebInfrastructurePlatform/9.2/Picklists/wars/sas.svcs.scs/ picklist DRIVER=/sas/config/Lev1/Web/Applications/SASSharedServices9.2/JDBCDrivers/icu4j. jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/log4j.jar: /sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.core.jar:/ sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.core.nls. jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.icons. contents.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/ sas.icons.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/ sas.icons.nls.jar:/sas/config/lev1/web/applications/sassharedservices9.2/ JDBCDrivers/sas.intrnet.javatools.jar:/sas/config/Lev1/Web/Applications/ SASSharedServices9.2/JDBCDrivers/sas.intrnet.javatools.nls.jar:/sas/config/Lev1/ Web/Applications/SASSharedServices9.2/JDBCDrivers/sas.nls.collator.jar:/sas/ config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.oda.tkts.jar:/ 7

12 sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.oda.tkts. nls.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas. security.sspi.jar:/sas/config/lev1/web/applications/sassharedservices9.2/ JDBCDrivers/sas.svc.connection.jar:/sas/config/Lev1/Web/Applications/ SASSharedServices9.2/JDBCDrivers/sas.svc.connection.nls.jar CLASSPATH=$UTILITIESDIR:$LAUNCHERJAR "$JAVA_JRE_COMMAND" \ -classpath "$CLASSPATH" \ -Djava.system.class.loader=com.sas.app.AppClassLoader \ -Dsas.app.launch.config="$PICKLISTS" \ -Dsas.app.repository.path="$SASVJR_REPOSITORYPATH" \ -Dsas.app.class.path="$UTILITIESDIR:$DRIVER" \ -Djava.security.auth.login.config=../Common/login.config \ -Xmx256m \ -Dscs.jndi.jndiName=sas/jdbc/SharedServices \ -Dscs.jndi.jdbcUrl=jdbc:sastkts://your-host-name: 2172?constring=\(DSN=SharedServices\) \ -Dscs.jndi.driver=com.sas.tkts.TKTSDriver \ \ -Dscs.jndi.pwd=your-password \ org.apache.jackrabbit.core.jcrcopyrepository $1 $2 exit 0 6. Execute the following command:./jcrcopyrepository.sh /SAS-configuration-directory/Lev1/Lev1/AppData /SASContentServer/Repository /SAS-configuration-directory/Lev1/Lev1 /AppData/SASContentServer/temp You are now using the file system as the temporary back end for the SAS Content Server. Next, configure the SAS Content Server to use SQL Server as the back-end database. 7. Change the name of the SAS Content Server repository from Repository to RepositoryTS. For a Windows operating environment, use the following command: move C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\Repository C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\RepositoryTS 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/RepositoryTS 8. 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 9. Copy the repository.sqlserver.xml file from the SASHOME/SASWebInfrastructurePlatform/9.2/ Static/wars/sas.svcs.scs/WEB-INF/templates directory to the /SAS-configurationdirectory/Lev1/AppData/SASContentServer/Repository directory that was created in the 8

14 12. Execute the following command:./jcrcopyrepository.sh /SAS-configuration-directory/Lev1/AppData /SASContentServer/temp /SAS-configuration-directory/Lev1/AppData /SASContentServer/Repository 13. Restart WebSphere. Step 10. Verify that the new database is the new back-end data store. To verify that the SAS Content Server is using SQL Server, save a new report in SAS Web Report Studio or add content from SAS Management Console to the SAS Content Server. The size of your tables will increase if the SAS Content Server is properly configured to use SQL Server. To verify that the Web Infrastructure Platform and Shared Services are using SQL Server, save a new alert in the SAS BI Dashboard. The size of your tables will increase if the Web Infrastructure Platform and Shared Services are properly configured to use SQL Server. Database Migration Instructions for the WebLogic Application Server Step 1: Extract the Web Infrastructure Platform and Shared Services data from SAS Table Server. Extract the data that is related to the Web Infrastructure Platform and Shared Services from SAS Table Server. To do this, use the SAS Migration Utility and package the data in a ZIP file. You use this file later to load the data into the new database. 1. Download the SAS Migration Utility (support.sas.com/demosdownloads/setupcat.jsp?cat=sas+migration+utility) and save it to a folder on your file system, such as C:\SMU. 2. Copy the contents of the smu.properties file that is located in the Appendix of this document and save it to a file on your system. 3. In the smu.properties file, update the values for the host name, port number, file path, user name, and password to match your environment. 4. Create the folder C:\SMU_packages on your file system. This is the location where the migration package will be created. The folder value should match the value for the SMU.Output.Dir property in the smu.properties file. 5. From the command prompt, change to the directory where the downloaded SAS Migration Utility is stored. 6. Submit the following command to create the migration package: smu92_32 -properties "path-to-your-smu.properties-file" -only biservmid Here is an example: 10 smu92_32 -properties "C:\smu.properties" -only biservmid

15 7. Go to the C:\SMU_packages\your-environment\biservmid directory and locate the WIP_database.zip file, which contains the data from SAS Table Server. Step 2. Create the new target database. Install and configure the new target database if you do not already have one running. If needed, consult the database administrator at your site for assistance. Step 3. Populate the database with the tables that are needed for the Web Infrastructure Platform and Shared Services. 1. Open the database_sqlserver.properties file from the SAS WIP Database Importer that you previously downloaded. Update the values for the following properties to match the values for your environment: database.host database.port database.name database.user.id database.user.password database.schema.pattern Note: The SQL Server database schema is the uppercased value of the log on ID (for example, ${DATABASE.USER.ID}). 2. Open the build.properties file from the SAS WIP Database Importer. Remove the comment delimiters from the following line: database.type=sqlserver 3. Update the values for the following properties to match the values for your environment: a. database.type specifies the type of the target database (for example, database.type=sqlserver. b. sql.scripts.data.dir specifies the absolute path to the data directory in the SASHOME location, which contains the SQL scripts for the Web Infrastructure Platform that are used to create its database tables, load its out-of-the-box data, and drop its database tables (for example, sql.scripts.data.dir=c:\\ Program Files\\SAS\\SASSharedServices\\9.2\\Config\\Deployment\\Data\\). c. database.zip.file specifies the absolute path to the v920m3 WIP_database.zip file from which records will be read and inserted into the target v920m3 database. The WIP_database.zip file is created by the SASSMU2 (for example, database.zip.file=c:\\public\\v920m3\dbimporter92m3 \\test\\sassmu2\\wip_database.zip). d. log4j.config.file specifies the Log4J configuration file which is used by the database importer for the Web Infrastructure Platform. Edit the log4j.properties file to specify the location of the log file (for example, log4j.config.file=file:///c:/public/v920m3/dbimporter92m3/log4j. properties). 11

16 e. java.maxmemory specifies the maximum amount of memory that can be used by the database importer for the Web Infrastructure Platform (Java application) (for example, java.maxmemory=2048m). 4. Open a command window and change to the SAS WIP Database Importer directory. Submit the createdatabasetables command to create the database tables for the Web Infrastructure Platform and Shared Services (for example, C:\DbImporter92m3> ant -f build.xml createdatabasetables). Step 4. Update the Web Infrastructure Platform and Shared Services data source that is defined in WebLogic. The initial installation created a data source named SharedServices that references SAS Table Server. This step redirects that reference to a new data source that relies on SQL Server. Update the values for the database name, host name, port number, user ID, and password for the SQL Server database Connection Pool in the WebLogic administrative console. On the SQL Server WebLogic application server, the values are available from the WebLogic Administration Console. Select SASDomain Services JDBC Data Sources SharedServices Configuration and then click the Connection Pool tab. Update the values for the new SQL Server database. Step 5. Update the configuration properties for the Web Infrastructure Platform and Shared Services. The SAS installation and configuration process stores metadata about the properties for Shared Services. Updating the metadata is a manual change to the configuration. Therefore, the properties must be updated to accommodate possible future migrations. Here are the steps to update the metadata for the configuration properties: 1. Start SAS Management Console and log on as sasadm (or another fully privileged user ID). 2. Click the Folders tab and select System Applications SAS Shared Services. 3. Select the SharedServices9.2 folder. 4. In the right pane, right-click SharedServices9.2 and select Properties. 5. Click the Configuration tab. 6. Specify the following values for the SharedServices properties: a. data.dbms.type: sqlserver b. dbms.biservmid.host: SQLServer-host-name c. dbms.biservmid.jdbc.dir: directory-path-containing-the-sqlserver-jdbcdriver-jar d. dbms.biservmid.name: SQLServer-database-name e. dbms.biservmid.port: SQLServer-port-number 12

17 f. dbms.biservmid.userid: SQLServer-userID g. dbms.biservmid.validation.query: select 1 from dual 7. Click OK to exit the dialog box, and then exit SAS Management Console. Step 6. Migrate the Web Infrastructure Platform and Shared Services from SAS Table Server to the new database. Migrate the data that was exported from SAS Table Server to the new database. 1. Open a command window and navigate to the directory for the SAS WIP Database Importer. 2. Submit the importdatabase command to create the Web Infrastructure Platform and Shared Services database tables (for example, C:\DbImporter92m3> ant -f build.xml importdatabase). Step 7. Update the workflow to use the proper dialect. Using the following steps, update the workflow to use the new database. 1. Open the sas.shared9.2.ear file. Then, within this EAR file, open the workflow.properties file, which resides in the \sas.workflow.war\web-inf\ directory. 2. Add a comment delimiter to the following line: workflow.hibernate.dialect=com.sas.workflow.engine.services.dao. TSFirebirdDialect Here is an example: workflow.hibernate.dialect=com.sas.workflow.engine.services.dao. TSFirebirdDialect 3. Remove the comment delimiter from the following line: workflow.hibernate.dialect=org.hibernate.dialect.sqlserverdialect Here is an example: workflow.hibernate.dialect=org.hibernate.dialect.sqlserverdialect 4. Redeploy the sas.shared9.2.ear file. Step 8. Populate the database with the tables that are needed for the SAS Content Server. The scripts that were needed to create the tables for the SAS Content Server were executed by the createdatabasetables command in the previous steps. 13

18 Step 9. Configure the SAS Content Server to use the new database as its repository. This section discusses the steps that are needed to migrate the stored SAS Content Server data from SAS Table Server to a SQL Server database. It also details the steps that are needed to configure the SAS Content Server for the new SQL Server database. In order to migrate the data, you need to convert the SAS Content Server from using SAS Table Server to using the file system and then to using SQL Server. Revert to the file system after you have configured the SAS Content Server for SAS Table Server. 1. Stop the WebLogic process. 2. Back up the following directory: SAS-configuration-directory/Lev1/AppData/SASContentServer 3. Create a new directory as follows: SAS-configuration-directory/Lev1/AppData/SASContentServer/temp 4. Copy the repository.xml file that resides in the SASHOME/SASWebInfrastructurePlatform/9.2/ Static/wars/sas.svcs.scs/WEB INF/templates/ directory to the SAS-configurationdirectory/Lev1/AppData/SASContentServer/temp directory. 5. Change directory to SAS-configuration-directory/Lev1/Web/Utilities. Verify that your JCRCopyRepository.sh script has only one set of JNDI arguments for SAS Table Server. It should look similar to the following: 14!/bin/sh -p JCRCopyRepository.sh. `dirname $0`/../../level_env.sh LAUNCHERJAR=$SASVJR_HOME/eclipse/plugins/sas.launcher.jar UTILITIESDIR=$LEVEL_ROOT/Web/Utilities PICKLISTS=/sas/SASWebInfrastructurePlatform/9.2/Picklists/wars/sas.svcs.scs/ picklist DRIVER=/sas/config/Lev1/Web/Applications/SASSharedServices9.2/JDBCDrivers/icu4j. jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/log4j.jar: /sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.core.jar:/ sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.core.nls. jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.icons. contents.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/ sas.icons.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/ sas.icons.nls.jar:/sas/config/lev1/web/applications/sassharedservices9.2/ JDBCDrivers/sas.intrnet.javatools.jar:/sas/config/Lev1/Web/Applications/ SASSharedServices9.2/JDBCDrivers/sas.intrnet.javatools.nls.jar:/sas/config/Lev1/ Web/Applications/SASSharedServices9.2/JDBCDrivers/sas.nls.collator.jar:/sas/ config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.oda.tkts.jar:/ sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.oda.tkts. nls.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas. security.sspi.jar:/sas/config/lev1/web/applications/sassharedservices9.2/ JDBCDrivers/sas.svc.connection.jar:/sas/config/Lev1/Web/Applications/ SASSharedServices9.2/JDBCDrivers/sas.svc.connection.nls.jar CLASSPATH=$UTILITIESDIR:$LAUNCHERJAR "$JAVA_JRE_COMMAND" \ -classpath "$CLASSPATH" \ -Djava.system.class.loader=com.sas.app.AppClassLoader \

19 -Dsas.app.launch.config="$PICKLISTS" \ -Dsas.app.repository.path="$SASVJR_REPOSITORYPATH" \ -Dsas.app.class.path="$UTILITIESDIR:$DRIVER" \ -Djava.security.auth.login.config=../Common/login.config \ -Xmx256m \ -Dscs.jndi.jndiName=sas/jdbc/SharedServices \ -Dscs.jndi.jdbcUrl=jdbc:sastkts://your-host-name: 2172?constring=\(DSN=SharedServices\) \ -Dscs.jndi.driver=com.sas.tkts.TKTSDriver \ \ -Dscs.jndi.pwd=your-password \ org.apache.jackrabbit.core.jcrcopyrepository $1 $2 exit 0 6. Execute the following command:./jcrcopyrepository.sh /SAS-configuration-directory/Lev1/Lev1/AppData /SASContentServer/Repository /SAS-configuration-directory/Lev1/Lev1 /AppData/SASContentServer/temp You are now using the file system as the temporary back end for the SAS Content Server. Next, configure the SAS Content Server to use SQL Server as the back-end database. 7. Change the name of the SAS Content Server repository from Repository to RepositoryTS. For a Windows operating environment, use the following command: move C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\Repository C:\SAS-configuration-directory\Lev1\AppData\SASContentServer\RepositoryTS 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/RepositoryTS 8. 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 9. Copy the repository.sqlserver.xml file from the SASHOME/SASWebInfrastructurePlatform/9.2/ Static/wars/sas.svcs.scs/WEB-INF/templates directory to the /SAS-configurationdirectory/Lev1/AppData/SASContentServer/Repository directory that was created in the previous step. Rename the file to repository.xml. The following example shows syntax for a UNIX environment: cp /SASHOME/SASWebInfrastructurePlatform/9.2/Static/wars/sas.svcs.scs/WEB- INF/templates/repository.sqlserver.xml Repository/repository.xml 10. Obtain the values for the database name, host name, port number, user ID, and password from the web application server. 15

21 Step 10. Verify that the new database is the new back-end data store. To verify that the SAS Content Server is using SQL Server, save a new report in SAS Web Report Studio or add content from SAS Management Console to the SAS Content Server. The size of your tables will increase if the SAS Content Server is properly configured to use SQL Server. To verify that the Web Infrastructure Platform and Shared Services are using SQL Server, save a new alert in the SAS BI Dashboard. The size of your tables will increase if the Web Infrastructure Platform and Shared Services are properly configured to use SQL Server. Database Migration Instructions for the JBoss Application Server Step 1. Extract the Web Infrastructure Platform and Shared Services data from SAS Table Server. Extract the data that is related to the Web Infrastructure Platform and Shared Services from SAS Table Server. To do this, use the SAS Migration Utility and package the data in a ZIP file. You use this file later to load the data into the new database. 1. Download the SAS Migration Utility (support.sas.com/demosdownloads/setupcat.jsp?cat=sas+migration+utility) and save it to a folder on your file system, such as C:\SMU. 2. Copy the contents of the smu.properties file that is located in the Appendix of this document and save it to a file on your system. 3. In the smu.properties file, update the values for the host name, port number, file path, user name, and password to match your environment. 4. Create the folder C:\SMU_packages on your file system. This is the location where the migration package will be created. The folder value should match the value for the SMU.Output.Dir property from the smu.properties file. 5. From the command prompt, change to the directory where the downloaded SAS Migration Utility is stored. 6. Submit the following command to create the migration package: smu92_32 -properties "path-to-your-smu.properties-file" -only biservmid Here is an example: smu92_32 -properties "C:\smu.properties" -only biservmid 7. Go to the C:\SMU_packages\your-environment\biservmid directory and locate the WIP_database.zip file, which contains the data from SAS Table Server. 17

22 Step 2. Create the new target database. Install and configure the new target database if you do not already have one running. If needed, consult the database administrator at your site for assistance. Step 3. Populate the database with the tables that are needed for the Web Infrastructure Platform and Shared Services. Create the Web Infrastructure Platform and Shared Services tables in SQL Server. 1. Open the database_sqlserver.properties file from the SAS WIP Database Importer that you previously downloaded. Update the values for the following properties to match the values for your environment: database.host database.port database.name database.user.id database.user.password database.schema.pattern Note: The SQL Server database schema is the uppercased value of the log on ID (for example, ${DATABASE.USER.ID}). 2. Open the build.properties file from the SAS WIP Database Importer. Remove the comment delimiters from the following line: database.type=sqlserver 3. Update the values for the following properties to match the values for your environment: a. database.type specifies the type of the target database (for example, database.type=sqlserver). b. sql.scripts.data.dir specifies the absolute path to the data directory in the SASHOME location, which contains the SQL scripts for the Web Infrastructure Platform that are used to create its database tables, load its out-of-the-box data, and drop its database tables (for example, sql.scripts.data.dir=c:\\ Program Files\\SAS\\SASSharedServices\\9.2\\Config\\Deployment\\Data\\). c. database.zip.file specifies the absolute path to the v920m3 WIP_database.zip file from which records will be read and inserted into the target v920m3 database. The WIP_database.zip file is created by the SASSMU2 (for example, database.zip.file=c:\\public\\v920m3\dbimporter92m3 \\test\\sassmu2\\wip_database.zip). d. log4j.config.file specifies the Log4J configuration file which is used by the database importer for the Web Infrastructure Platform. Edit the log4j.properties file to specify the location of the log file (for example, log4j.config.file=file:///c:/public/v920m3/dbimporter92m3/ log4j.properties). 18

23 e. java.maxmemory specifies the maximum amount of memory that can be used by the database importer for the Web Infrastructure Platform (Java application) (for example, java.maxmemory=2048m). 4. Open a command window and change to the SAS WIP Database Importer directory. Submit the createdatabasetables command to create the database tables for SAS the Web Infrastructure Platform and Shared Services (for example, C:\DbImporter92m3> ant -f build.xml createdatabasetables). Step 4. Update the Web Infrastructure Platform and Shared Services data source that is defined in JBoss. The initial installation created a data source named SharedServices that referenced SAS Table Server. This step redirects that reference to a new data source that relies on SQL Server. 1. Copy the SQL Server JDBC driver JAR file ojdbc6.jar to the /JBoss-home/server/SASServer1/lib directory. 2. Open the SharedServices ds.xml file that is located in the /JBoss-home/server/SASServer1 /deploy/ directory. Update the values in the file to point to the SQL Server database, as shown in the following example: <?xml version="1.0" encoding="utf-8"?> <datasource> <local-tx-datasource> <driver-class>com.microsoft.sqlserver.jdbc.sqlserverdriver</driver-class> <jndi-name>sas/jdbc/sharedservices</jndi-name> <connection-property name="stmtpooling">0</connection-property> <connection-property name="constring">(dsn=sharedservices)</connection-property> <connection-url>jdbc:sqlserver://host1433;databasename= SharedServices;SelectMethod=cursor</connection-url> <user-name>your-user-name</user-name> <password>your-password</password> </local-tx-datasource> </datasource> Step 5. Update the configuration properties for the Web Infrastructure Platform and Shared Services. The SAS installation and configuration process stores metadata about the properties for Shared Services. Updating the metadata is a manual change to the configuration. Therefore, the properties must be updated to accommodate for possible future migrations. Here are the steps to update the metadata for the configuration properties: 1. Start SAS Management Console and log on as sasadm (or another fully privileged user ID). 2. Click the Folders tab and select System Applications SAS Shared Services. 3. Select the SharedServices9.2 folder. 4. In the right pane, right-click SharedServices9.2 and select Properties. 5. Click the Configuration tab. 6. Specify the following values for the SharedServices properties: 19

24 a. data.dbms.type: sqlserver b. dbms.biservmid.host: SQLServer-host-name c. dbms.biservmid.jdbc.dir: directory-path-containing-the-sqlserver-jdbcdriver-jar d. dbms.biservmid.name: SQLServer-database-name e. dbms.biservmid.port: SQLServer-port-number f. dbms.biservmid.userid: SQLServer-userID g. dbms.biservmid.validation.query: select 1 from dual 7. Click OK to exit the dialog box, and then exit SAS Management Console. Step 6. Migrate the Web Infrastructure Platform and Shared Services from SAS Table Server to the new database. Migrate the data that was exported from SAS Table Server to the new database. 1. Open a command window and navigate to the directory for the SAS WIP Database Importer. 2. Submit the importdatabase command to create the Web Infrastructure Platform and Shared Services database tables (for example, C:\DbImporter92m3> ant -f build.xml importdatabase). Step 7. Update the workflow to use the proper dialect. Update the workflow in order to use the new database. 1. Open the sas.shared9.2.ear file. Within this EAR file open workflow.properties, which resides in the \sas.workflow.war\web-inf\ directory. 2. Add a comment delimiter to the following line: workflow.hibernate.dialect=com.sas.workflow.engine.services.dao. TSFirebirdDialect Here is an example: workflow.hibernate.dialect=com.sas.workflow.engine.services.dao. TSFirebirdDialect 3. Remove the comment delimiter from the following line: workflow.hibernate.dialect=org.hibernate.dialect.sqlserverdialect Here is an example: workflow.hibernate.dialect=org.hibernate.dialect.sqlserverdialect 4. Redeploy the sas.shared9.2.ear file. 20

25 Step 8. Populate the database with the tables that are needed for the SAS Content Server. The scripts that were needed to create the tables for the SAS Content Server were executed by the createdatabasetables command in the previous steps. Step 9. Configure the SAS Content Server to use the new database as its repository. This section discusses the steps that are needed to migrate the stored SAS Content Server data from SAS Table Server to a SQL Server database. It also details the steps that are needed to configure the SAS Content Server for the new SQL Server database. In order to migrate the data, you need to convert the SAS Content Server from using SAS Table Server to using the file system and then to using SQL Server. Revert to the file system after you have configured the SAS Content Server for SAS Table Server. 1. Stop the JBoss process. 2. Back up the following directory: SAS-configuration-directory/Lev1/AppData/SASContentServer 3. Create a new directory as follows: SAS-configuration-directory/Lev1/AppData/SASContentServer/temp 4. Copy the repository.xml file that resides in the SASHOME/SASWebInfrastructurePlatform/9.2/ Static/wars/sas.svcs.scs/WEB INF/templates/ directory to the SAS-configurationdirectory/Lev1/AppData/SASContentServer/temp directory. 5. Change directory to SAS-configuration-directory/Lev1/Web/Utilities. Verify that your JCRCopyRepository.sh script has only one set of JNDI arguments for SAS Table Server. It should look similar to the following:!/bin/sh -p JCRCopyRepository.sh. `dirname $0`/../../level_env.sh LAUNCHERJAR=$SASVJR_HOME/eclipse/plugins/sas.launcher.jar UTILITIESDIR=$LEVEL_ROOT/Web/Utilities PICKLISTS=/sas/SASWebInfrastructurePlatform/9.2/Picklists/wars/sas.svcs.scs/ picklist DRIVER=/sas/config/Lev1/Web/Applications/SASSharedServices9.2/JDBCDrivers/icu4j. jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/log4j.jar: /sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.core.jar: /sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.core.nls. jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.icons. contents.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/ sas.icons.jar:/sas/config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/ sas.icons.nls.jar:/sas/config/lev1/web/applications/sassharedservices9.2/ JDBCDrivers/sas.intrnet.javatools.jar:/sas/config/Lev1/Web/Applications/ SASSharedServices9.2/JDBCDrivers/sas.intrnet.javatools.nls.jar:/sas/config/Lev1/ Web/Applications/SASSharedServices9.2/JDBCDrivers/sas.nls.collator.jar:/sas/ config/lev1/web/applications/sassharedservices9.2/jdbcdrivers/sas.oda.tkts.jar:/ 21

FileNet Business Activity Monitor (BAM) Release Notes Release 3.6.0 September 2006 FileNet is a registered trademark of FileNet corporation. All other product and brand names are trademarks or registered

About This Tutorial 1Creating an End-to-End HL7 Over MLLP Application 1.1 About This Tutorial 1.1.1 Tutorial Requirements 1.1.2 Provided Files This tutorial takes you through the steps of creating an end-to-end

Setting up the Oracle Warehouse Builder Project Purpose In this tutorial, you setup and configure the project environment for Oracle Warehouse Builder 10g Release 2. You create a Warehouse Builder repository

BusinessObjects Enterprise XI Release 2 How to configure an Internet Information Services server as a front end to a WebLogic application server Overview Contents This document describes the process of

IBM WebSphere Application Server Version 7.0 Centralized Installation Manager for IBM WebSphere Application Server Network Deployment Version 7.0 Note: Before using this information, be sure to read the

Getting Started using the SQuirreL SQL Client The SQuirreL SQL Client is a graphical program written in the Java programming language that will allow you to view the structure of a JDBC-compliant database,

Using Microsoft Windows Authentication for Microsoft SQL Server Connections in Data Archive 2014 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means

IBM Cúram Social Program Management Cúram Deployment Guide for WebSphere Application Server Version 6.0.4 Note Before using this information and the product it supports, read the information in Notices

Using the DataDirect Connect for JDBC Drivers with WebLogic 8.1 Introduction This document explains the steps required to use the DataDirect Connect for JDBC drivers with the WebLogic Application Server

Copyright IBM Corporation 2010 All rights reserved WebSphere Business Monitor V7.0 What this exercise is about... 2 Lab requirements... 2 What you should be able to do... 2 Introduction... 3 Part 1: Install

LAE 5.1 Windows Server Installation Guide Copyright THE CONTENTS OF THIS DOCUMENT ARE THE COPYRIGHT OF LIMITED. ALL RIGHTS RESERVED. THIS DOCUMENT OR PARTS THEREOF MAY NOT BE REPRODUCED IN ANY FORM WITHOUT

E-mail Listeners 6 E-mail Formats You use the E-mail Listeners application to receive and process Service Requests and other types of tickets through e-mail in the form of e-mail messages. Using E- mail

44 Working with WebSphere 4.0 This chapter is for developers who are familiar with WebSphere Application Enterprise Server, version 4.0 (WAS 4.0) and would like to deploy their applications using WAS 4.0.

HOW TO DEPLOY AN EJB APLICATION IN WEBLOGIC SERVER 11GR1 Last update: June 2011 Table of Contents 1 PURPOSE OF DOCUMENT 2 1.1 WHAT IS THE USE FOR THIS DOCUMENT 2 1.2 PREREQUISITES 2 1.3 BEFORE DEPLOYING

Jboss Developer Studio Installation By : Shivam Dubey Brief Description : This document will help you to install the Jboss Developer Studio through terminal and will also guide that how you can configure

Advantage Joe Deployment Guide for WebLogic v8.1 Application Server This documentation and related computer software program (hereinafter referred to as the Documentation ) is for the end user s informational

APIS CARM NG Quick Start Guide for MS Windows The information contained in this document may be changed without advance notice and represents no obligation on the part of the manufacturer. The software

Technical Note Overview This document summarizes the steps of deploying ActiveVOS on the IBM WebSphere Platform. Legal Notice The information in this document is preliminary and is subject to change without