Select Page

Art of BI: OBIEE 11g – Automate Weblogic to Avoid Prompt for Credentials at Start-up

Christian Screen | | October 8, 2010

With the introduction of Weblogic as the core application server for OBIEE 11g there are some learning curves thrown at most organizations.  One of those curves is going to be automating the start-up of the managed server or WebLogic Admin server at start up.  This post quickly takes a look at one hiccup that can be quickly overcome when starting up the WebLogic server.


You may have noticed that when you start the Weblogic Server that you are often prompted for the Weblogic Admin (username/password entered when installing OBI11g or EPM 11.1.2) credentials once the start script begins to run.  This is a security mechanism of WebLogic basically saying that you shouldn’t start up or shutdown the server unless you are a provision users of the default security realm.  This only makes sense, right?

So, if you are trying to automate this start-up process of your app server, how best do you over come this security guard?  Easily enough, you will simply create a file and place it under a specific location in the WebLogic install path, DOMAIN_NAME/servers/SERVER_NAME/security, where DOMAIN_NAME is the name of the directory in which you located the domain and SERVER_NAME is the name of the server (For OBI 11g the AdminServer is all that you need to implement this for). Under the following path is where you would add the file


The file will contain two rows each having a name/value pair for username and password respectively.  The name of the file must be called  This is the simplest way to accomplish this.

Another approach would be to use the scripting capability of WebLogic which we won’t discuss here.  Please take a look at some of the references below for product documentation and detailed steps.


Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

ORA-12154: TNS:could not resolve the connect identifier specified

Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.

Jeremiah Wilton | March 4, 2009

12c Upgrade Bug with SQL Tuning Advisor

Learn the steps to take on your Oracle upgrade 11.2 to 12.1 if you’re having performance problems. Oracle offers a patch and work around to BUG 20540751.

Megan Elphingstone | March 22, 2017

Oracle EPM Cloud Vs. On-Premises: What’s the Difference?

EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.

Bobby Ellis | April 10, 2018

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.


Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.