Migrate Enterprise Manager Application Roles and Weblogic Users and Groups between environments

Managing users across environments, when using the built-in Weblogic LDAP was a tedious process. What I have found to work well is create the users once, and then have a script which caries them across to the rest of the environments. This has been very useful in our Development and Test environments when getting the users seeded.

The Enterprise Manager (EM) migration script utilizes a very cool java program that ArtofBI developed and posted to Github. I've tweaked the code a bit for my needs, so attached to this post also includes the modified javasource and complied JAR.

Continue after the break for links to the files, and example scripts for both Enterprise Manager and Weblogic.

Changing password of the MDS and BIPLATFORM schemas used by OBIEE 11g

At my current engagement, we are required to change the passwords for everything every 60 days. After doing some research I found a blog post by someone who showed how to do this from Enterprise Manager, but they only covered three of the four locations to change the password. As I have mentioned previously, I like automation, so I build a script which takes care of all the tasks.

After the jump is an example script, along with the python for WLST, to perform this task.

Scripted RPD deployments using UDML and WLST

Automating the RPD deployment in OBIEE 10g was as simple as doing an SCP of the RPD to the OBIEE server, and then bounce the processes. With OBIEE 11g, RPD deployments are now handled through Weblogic, so we need to take some additional steps. Luckily these can be easily scripted thanks to WLST.

After the jump is a script which can be used to do OBIEE 11g RPD deployments. This script assumes you have setup ssh keys on the various servers so you can login without typing a password (http://www.linuxproblem.org/art_9.html).

Scripted OBIEE 11g Web Catalog deployments using runcat.sh and WLST

I had never looked deeply into automating the OBIEE Web Catalog, as on previous engagements I had a technical architecture team which handled all deployments. They were used to doing a manual process utilizing the Catalog Manager. On my latest engagement, I am the technical architecture team, and I like automation.

After poking around, I found that you can call the catalog manager form the command line, and along with WLST scripting, you can do a fully automated web catalog deployment.

After the jump is a script which can be used to do OBIEE 11g web catalog deployments. This script assumes you have setup ssh keys on the various servers so you can login without typing a password (http://www.linuxproblem.org/art_9.html).