Skip navigation.

Michael Armstrong-Smith

Syndicate content
Michaelnoreply@blogger.comBlogger166125
Updated: 10 hours 37 min ago

Are you worried about what to do now that Discoverer is almost out of support

Wed, 2016-04-13 03:52
Hello everyone
Like me, if you are a big user of Discoverer, you would have been alarmed at the news a few years ago that Oracle was dropping the tool.

Well, once I got over my alarm I started to think about how my clients could maximize their use of the at times millions of dollars of investment.

Oracle Corporation’s statement of direction implies that they will not force you off of Discoverer and on to another tool. It is important for you to understand, however that like all software Discoverer will one day be phased out in order to make way for more modern BI solutions.

You currently have three options: Protect / Extend / Evolve

  1. Protect your investment by staying with Discoverer, continuing to receive Oracle’s outstanding support until it runs out, after which you will be on your own
  2. Extend you your investment by continuing to use Discoverer while integrating to other Oracle BI tools such as Oracle BI Enterprise Edition (OBIEE)
  3. Evolve your investment by formulating a strategy to fully migrate to another tool, perhaps one of Oracle's other BI tools such as OBIEE, or to a third party tool such as SplashBI owned by Eis Technilogies
I will address more on option 3 in upcoming posts.

Are you having trouble starting Weblogic from a Windows service

Wed, 2016-04-13 03:26
Are you having trouble starting Weblogic on Windows and thus unable to start the WLS_DISCO service? If so, you can start Wenlogic from the command line.

To start Weblogic from the command line, follow these steps:
  1. Open a CMD window
  2. Navigate to the bin folder for Weblogic. Mine is located at C:\oracle\Middleware\user_projects\domains\ClassicDomain\bin
  3. Run startweblogic.cmd
  4. Provide a username - in my case weblogic
  5. Provide the password
  6. When started, leave the CMD window open

Next, I started the Node Manager manually as follows:
  1.  Open a second CMD window
  2. Navigate to the bin folder for Node Manager. Mine is located at C:\oracle\Middleware\wlserver_10.3\server\bin
  3. Run startnodemanager.cmd
  4. Provide a username - in my case weblogic
  5. Provide the password
  6. When started, leave the CMD window open