Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Information Server This presentation describes the steps needed to move the XMeta repository from one database server to another for Information Server version 8.0.1 and version 8.1. Objectives Objectives Backing up XMeta, IS, and key files Update Information Services Framework (ISF) configuration Update XMeta username and password Update WebSphere® Application Server configuration The objectives of this presentation are to describe what needs to be backed up and how to update the Information Services Framework configuration, referred to as the ISF configuration. This presentation will also describe how to update the XMeta user name and password, and what changes need to be made to WebSphere. Backup and restore 3 Backup and restore Backup backup XMeta, Information Server, and WebSphere Backup all files being changed InformationServer/ASBServer/bin/sql/database.properties InformationServer/ASBServer/apps/lib/ojb-conf.jar InformationServer/ASBServer/apps/sql/ojb-conf-pojo.jar – 801 only InformationServer/ASBServer/etc/package.compiler.properties – 801 only Do not leave copy of ojb-conf.jar in Information Server folder hierarchy Backup XMeta database Restore Restore XMeta to new target system Before you make any changes to XMeta, Information Server, or WebSphere, it is good practice to take a complete backup of all three installations. It is safest to do a cold backup of the WebSphere Application Server by stopping WebSphere before you do the backup. It is also good practice to make a copy of all the files that will be changed during this process to make it easier to revert back if necessary. The files that are key to make copies of are displayed on this slide. Ensure the backup of ojb-conf.jar is not left in the IBM Information Server folder hierarchy. Backup the XMeta database on the source system and restore to the target system using the backup and restore tools provided with the database. Backup the affected files before changing them in this procedure. Updates to ISF Configuration (1 of 3) 4 Updates to ISF Configuration (1 of 3) Stop WebSphere Application Server cd /opt/IBM/WebSphere/AppServer/bin ./stopServer.sh server1 –username –password Create temporary empty directory and make it current working directory mkdir /tmp/isftmp cd /tmp/isftmp Extract ojb-conf.jar into temp directory /opt/IBM/WebSphere/AppServer/java/bin/jar xf /opt/IBM/InformationServer/ASBServer/apps/lib/ojb-conf.jar The next step is to update the ISF configuration. To do this, first you will need to stop WebSphere. cd into the Websphere/AppServer/bin directory and run ./stopServer.sh server1 –username –password , where is your wasadmin username and is your wasadmin password. After stopping the WebSphere Application Server, create a temporary directory and set it as your current working directory by running: mkdir /tmp/isftmpcd /tmp/isftmp While in your newly created temp directory, extract the ojb-conf.jar file using the jar utility of a JDK™. For example, the JDK in WebSphere. If WebSphere and Information Server are installed in the default directories, the command is /opt/IBM/WepSphere/AppServer/java/bin/jar xf /opt/IBM/InformationServer/ASBServer/apps/lib/ojb-conf.jar. This command will extract ojb-conf.jar and place the contents in your temp directory. Updates to ISF Configuration (2 of 3) Updates to ISF Configuration (2 of 3) Edit repository_database.xml Linux®/UNIX®: vi repository_database.xml Windows®: Notepad repository_database.xml DB2® dbalias=”//host:50000/dbname” Oracle dbalias=”oracle://host:1521;SID=dbname” MS SQLServer dbalias=”sqlserver://host:1433;DatabaseName=dbname” The next step is to edit the repository_database.xml file that is in your temp directory. Use the vi command for Linux and UNIX or open the file in Notepad if on Windows. Search for the dbalias attribute. Use the table displayed on this slide to correctly update this field. Edit the dbalias attribute with the right host, port and dbname value, and save the file. Updates to ISF Configuration (3 of 3) 6 Updates to ISF Configuration (3 of 3) Rejar ojb-conf.jar with updated information /opt/IBM/WebSphere/AppServer/java/bin/jar cf /opt/IBM/InformationServer/ASBServer/apps/lib/ojb-conf.jar . 8.1 - Remove temp directory 8.0.1 - Delete all files within temp directory After updating the dbalias attribute, you can now re-jar ojb-conf.jar with the updated repository_database.xml file using the jar utility of a JDK. For example, the JDK in WebSphere. Be sure you are still in your temp directory. If WebSphere and Information Server are installed in the default directories, the command is /opt/IBM/WebSphere/AppServer/java/bin/jar cf /opt/IBM/InformationServer/ASBServer/apps/lib/ojb-conf.jar . You must remember to put the “space dot” at the end of the jar command. After this step is completed, you need to clean up the temp directory. If you are using 8.1, you should delete the temporary directory. If you are on 8.0.1, you need to remove all the files under the temp directory but leave the directory itself as you will need to use it again in the next step. Updates to ISF Configuration – 8.0.1 ONLY (1 of 2) Updates to ISF Configuration – 8.0.1 ONLY (1 of 2) Repeat dbalias modification to ojb-conf-pojo.jar Extract ojb-conf-pojo.jar /opt/IBM/WebSphere/AppServer/java/bin/jar xf /opt/IBM/InformationServer/ASBServer/apps/sql/ojb-conf-pojo.jar Change dbalias in repository_database.xml Jar ojb-conf-pojo.jar /opt/IBM/WebSphere/AppServer/java/bin/jar cf /opt/IBM/InformationServer/ASBServer/apps/sql/ojb-conf-pojo.jar . The next steps are for the Information Server 8.0.1 only. If you are using version 8.1, skip this step. Next, while in your temp directory, you will need to extract the ojb-conf-pojo.jar file using the jar utility of a JDK™. For example, the JDK in WebSphere. Repeat the same modification of the dbalias attribute in the repository_database.xml file as you just made for the ojb-conf.jar file and then re-jar ojb-conf-pojo.jar. Updates to ISF Configuration – 8.0.1 ONLY (2 of 2) Updates to ISF Configuration – 8.0.1 ONLY (2 of 2) Edit InformationServer/ASBServer/etc/package.compiler.properties Look for correct Parameter Key DB2 PackageCompiler.connectionURL.db2_8_nls Oracle PackageCompiler.connectionURL.oracle10g_nls MS SQLServer PackageCompiler.connectionURL.sqlserver_nls DB2 jdbc:db2://host:50000/dbname Oracle jdbc:ibm:oracle://host:1521;SID=dbname MS SQLServer jdbc:ibm:sqlserver://host:1433;DatabaseName=dbname Parameter value format The next steps are for Information Server 8.0.1 only. If you are using version 8.1, skip this step. Edit the package.compiler.properties file located in the InformationServer/ASBServer/etc directory. Look for the PackageCompiler.connectionURL parameter key associated with your XMeta database. Update the host, port and dbname with the new values and save the file. Updates to ISF configuration Updates to ISF configuration Edit database.properties Linux/UNIX: vi /opt/IBM/InformationServer/ASBServer/bin/sql/database.properties Windows: notepad C:\IBM\InformationServer\ASBServer\bin\sql\database.properties Update URL parameter Example: url=jdbc\:db2\://NewServer.com\:50008/XMeta Edit the database.properties file in the InformationServer/ASBServer/bin/sql directory. Update the URL parameter to reflect the new repository server name and port. After updating, save the file. Update XMeta username and password Update XMeta username and password Run AppServerAdmin.sh command Linux/UNIX: /opt/IBM/InformationServer/ASBServer/bin/AppServerAdmin.sh -db -user -password Windows: C:\IBM\InformationServer\ASBServer\bin\AppServerAdmin.bat -db -user -password

Start WebSphere Application server as root cd /opt/IBM/WebSphere/AppServer/bin ./startSever.sh server1 To complete the updates to the ISF configuration, run the AppServerAdmin.sh command to update the XMeta username and password. The command can be found in the InformationServer/ASBServer/bin directory. Replace the with your XMeta Database username and the with the correct password. Once the AppServerAdmin command has run successfully, as root, restart WebSphere. cd to the WebSphere/AppServer/bin directory and type ./startServer.sh server1. Update WebSphere Application Server configuration (1 of 6) Update WebSphere Application Server configuration (1 of 6) Login to WebSphere Application Sever Administrative console https://:9043/ibm/console Login to the WebSphere Application Server Administrative Console. Click the Resources tab on the left side and then click JDBC Providers underneath. In the middle of the screen, select the server : server1 radio button, and click Apply. Next click ASB JDBC Provider link in the box below the Apply button. Update WebSphere Application Server configuration (2 of 6) Update WebSphere Application Server configuration (2 of 6) In the ASB JDBC Provider window, click Data sources under Additional Properties on the right side of the screen. Update WebSphere Application Server configuration (3 of 6) Update WebSphere Application Server configuration (3 of 6) Open each data Source listed and perform steps listed You may have more than one data source listed. Perform the steps described on each data source in the list. Click the link for the data source to be modified. Update WebSphere Application Server configuration (4 of 6) Update WebSphere Application Server configuration (4 of 6) Modify connection properties – DB2 For XMeta on DB2, scroll to the bottom of the screen for the data source and modify the connection properties as required. Click Apply. Update WebSphere Application Server configuration (5 of 6) Update WebSphere Application Server configuration (5 of 6) Modify connection properties – Oracle and SQL Server For XMeta on Oracle and SQL Server, on the Configuration tab, click Custom Properties on the right side under the Additional Properties heading. Once in Custom Properties, click the settings that have changed and set them to the appropriate values. Click Apply. Update WebSphere Application Server configuration (6 of 6) Update WebSphere Application Server configuration (6 of 6) In the Messages box at the top of the page click Save to save to the master configuration. Next, click the Save button in the next page. Test connection Test connection Test connection Stop and restart WebSphere Once the changes have been saved, test your new connection by clicking the Test connection button at the top of the Data Sources page where you made the server changes. If the connection is successful, you will see a message at the top of the screen indicating success. If it is unsuccessful, go back and check the modified data source settings. Once the test completes successfully, go back and modify the remaining data sources in the same manor. After all changes have been made, saved, and successfully tested, stop and restart WebSphere. Feedback Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send email feedback: mailto:iea@us.ibm.com?subject=Feedback_about_XmetaRepository.ppt This module is also available in PDF format at: ../XmetaRepository.pdf You can help improve the quality of IBM Education Assistant content by providing feedback. Trademarks