A little delayed, but it’s there, the BRtools studio for Oracle. A new fresh graphical way of doing your Oracle database administration. For more information on the functionality see the blog of Markus Maurer on SAP BR*Tools Studio for Oracle: Prepare for Lift-Off (SAP BR*Tools Studio for Oracle: Prepare for Lift-Off) </p><p> !https://weblogs.sdn.sap.com/weblogs/images/251969002/brtools.jpg|height=425|alt=brtools|width=571|src=https://weblogs.sdn.sap.com/weblogs/images/251969002/brtools.jpg!</p><p>So finally you can get rid of the command-line and start working in a nice, fancy graphical environment. At least…. if you overcome some challenges that are not explained in very much detail in the installation guide (which can be found here: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6049ab24-f948-2b10-929e-eda13ff1236f. </p><p>In this blog I will try to help solve some pain points that need to be overcome when installing the SAP BRtools studio for Oracle. Starting point is to use the above mentioned guide since this describes in high-level the steps needed. I will zoom in on some of these steps that might need more explanation.
The communication between client and server goes via HTTPS. A necessary step to make this work is to “Set up the keystore file on the BRTools Studio host for incoming client calls”. This step is not explained in detail in the installation guide but is important. There are two ways of working, you can either use an existing keystore or create a new one. The next steps show how to define your own on an existing Oracle database server running on Suse Linux Enterprise Server 10. On other operating system the commands should not differ that much since the tool used is a generic Java tool.</p><p> </p><p>1. Log on as <sid>ad on your Oracle database server and use the keytool to generate a keystore file:</p><p># keytool -genkey -alias studiocert -keyalg RSA -keysize 1024 -dname “CN=<FQDN>,OU=BRTOOLS,O=SAP,L=Amsterdam,C=NL” -keypass <password> -keystore server_keystore.jks -storepass <password></p><p>The above command is a way of creating your own keystore file called server_keystore.jks in your /home/<sid>adm/ directory. For FQDN you can fill you fully qualified domain name of the server and for <password> you can specify you own password).Also your private key is generated.</p><p>A check can be done via</p><p># keytool -list -v -keystore server_keystore.jks – storepass <password> </p><p>2. To turn your private key into a CSR (certificate Signing Request) use:</p><p># keytool -certreq -v -alias studiocert -file csr.pem -keypass <password> -storepass <password> -keystore server_keystore.jks </p><p>This creates a file called csr.pem. This CSR needs to be signed either by your own internal Certification Authority of by an external one. A temporary certificate can be obtained via for example Verisign. See https://www.verisign.com/ (https://www.verisign.com/) and click on SSL trial. Follow the procedure and copy the certificate response in a new file called servername-signed-cert.pem or use the retreived singed certificate from your internal CA. Also obtain the root certificate via your CA or an external party and put it in a file called root.pem. </p><p>3. Import both certificates into your keystore:</p><p>Rootcertificate:</p><p># keytool -import -v noprompt -trustcacerts -alias rootcert -fileroot.pem -keystore server_keystore.jks -storepass <password></p><p>Own signed certificate</p><p># keytool -import -v -alias studiocert -file servername-signed-cert.pem -keystore server_keystore.jks -keypass <password> -storepass <password></p><p>Now your keystore is created. Use the path and name of the keystore and the password when installing the SAP BRtools Studio for Oracle. This is explained in the official installation guide.
After installation the server needs to be started and from then on you can log on via your browser. Pay attention here because the username is CASE-sensitive so the username must be typed as “Administrator” with a capital A.
From now on the rest of the configuration is well described in the official guide. One last point of attention is the creation of a database user. Depending on the rights you want to give to a user you can assign roles. Below is an example: