![]() On the Capture page, select the older BMC Release Process Management database so that it appears in the list on the right, and then click Next.On the Source Database page, set Mode to Online, select the MySQL connection of BMC Release Process Management that you just created as the source database connection (from the older version of the product), and then click Next.On the Project page, specify all access details, including project name and output directory, and then click Next.Click Test to ensure that the connection is successful, and then click Save.Specify all access details for the MySQL server, including a super user and SID.Click the plus icon to create new connection.On the Repository page in the displayed wizard, create a connection to the MySQL server:.Navigate the Connections tree view to the list of database tables for the new Oracle connection, and delete all the existing tables and indexes so that all of the tables are clean.Click the Oracle tab, and specify all the access details (including a super user and database SID) for the Oracle server. ![]() Create a connection to the new Oracle database:.Click Test to ensure that the connection is successful.Click the MySQL tab, and specify all the access details of the MySQL server database.Navigate the Connections tree view, right-click the root node, and select New Connection.Create a connection to the MySQL database:.Add the MySQL JAR file location by specifying the full path (including the JAR file name).Navigate the tree view and click Data Modeler\Third Party JDBC Drivers.Back up the Oracle database that was installed by the installer of the newer version of BMC Release Process Management.Back up the MySQL server database of the previous version of BMC Release Process Management.Log on to the product with the same credentials as used in the previous product version.After the database schema migrates successfully from the old product version to the new product version (this might take some time), start the Tomcat service for the new BMC Release Process Management installation.Ensure that the PATH environment variable includes C:\BRPM\lib\jruby\bin and that no other ruby runtimes are specified in this variable.Open a command prompt and switch to the directory where BMC Release Process Management is installed (for example, C:\BRPM\server).To migrate from a Postgres database to an Oracle database, use the same migration task, but use the Postgres Java Database Connectivity Java Archive (JDBC JAR) while configuring the source connection.To migrate from a MySQL database to an Oracle database, see migrating from MySQL to Oracle.Migrate data from the old database to the new database:.Specify a new, unique name for the new database, such as brpm_2_6 or brpm_4_3. During the installation, do notspecify the same database used by the older version of the product, so that it does not get overwritten. Install BMC Release Process Management using the standard installer, as described in installing directly or installing silently.Ensure that Remote Desktop Connection is available to the server that you want to host the newer version of BMC Release Process Management.To migrate the database schema to the newer product version The Postgres database service, if installed, is running.The Tomcat service for the previous version of BMC Release Process Management is shut down.The Oracle user account has sufficient privileges to create, update, delete, and manage permissions on tables.You have successfully installed the newer version of BMC Release Process Management with an Oracle database.You have downloaded MySQL Java Database Connectivity Java Archive (JDBC JAR) for the appropriate MySQL server version.MySQL server is configured for access to the client computer and the previous version of BMC Release Process Management is installed and running.You have downloaded SQL Developer version 3.0 from the Oracle website and have installed it on your computer (usually the client computer).Your environment complies with the system requirements.Ensure that the following conditions exist:
0 Comments
Leave a Reply. |