Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 - Additional links:

This presentation is also available as PDF: XmetaRepository.pdf

Start WebSphere Application server as root cd /opt/IBM/WebSphere/AppServer/bin ./startSever.sh server1 11 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Update Version.xml Update /Version.xml on InformationServer server Open Version.xml in text editor Locate XML element Example: Modify value attribute with new XMeta server name SQLServer with named instances required format value= myserver\named_instance Locate next XML element Example: Modify value attribute with new port number 12 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Update WebSphere Application Server configuration (1 of 6) Login to WebSphere Application Sever Administrative console https://:9043/ibm/console 13 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Update WebSphere Application Server configuration (2 of 6) 14 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Update WebSphere Application Server configuration (3 of 6) Open each data Source listed and perform steps listed 15 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Update WebSphere Application Server configuration (4 of 6) Modify connection properties DB2 16 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Update WebSphere Application Server configuration (5 of 6) Modify connection properties Oracle and SQL Server 17 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Update WebSphere Application Server configuration (6 of 6) 18 Relocating the XMeta repository for Information Server version 8.0.1 and 8.1 Test connection Test connection Stop and restart WebSphere 19 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. 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. 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. 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/isftmp then cd /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. Use the command shown on this slide for your version of Information Server. You will need to adjust your path to the Information Server base directory to match your installation. This command will extract ojb-conf.jar and place the contents in your temp directory. 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. 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. Use the command displayed on this slide for your version of Information Server to rejar the file. You will need to adjust your path to the Information Server base directory to match your installation. 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. 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. The next steps are still 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. 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. 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. Next, update the Version.xml file. This file contains the installation records that are used by the installation program. Keeping the file current avoids problems with future installations. The Version.xml file is located in the IBM InfoSphere Information Server installation directory on the same server as the ojb-conf.jar file. Open the Version.xml file in a text editor and locate the Property name = XMetaDatabaseHost XML element. Modify the value attribute to contain the correct XMeta server name. Note that if you are using SQL Server with named instances, you will need to use the format of servername\named_instance for the XMeta server name. Next you need to locate the Property name= XMetaDatabasePortNumber XML element. Modify the value for the port number if your port number has changed. Save your changes. 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. In the ASB JDBC Provider window, click Data sources under Additional Properties on the right side of the screen. 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. For XMeta on DB2, scroll to the bottom of the screen for the data source and modify the connection properties as required. Click Apply. 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. 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. 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.