Andreas' Adventures

For a training I installed a WebCenter Suite environment on an Oracle Enterprise Linux. I ran into two problems. First I couldn't start the AdminServer. The logfile told me that the JDBC to mdsSpaces failed due to a Socket time out. Took me some time to realize this, but the reason was that I had configured the VirtualBox with a DNS (on the Windows host). Therefore the JDBC calls went out to seek for the database - which timed out. The second issue I had (and still have) is that after starting the NodeManager and AdminServer I couldn't start the WC_Spaces Server from inside the WebLogic Console. I have no solution for this yet, only a work-around. When I start the WC_Spaces from the commandline as a Managed Server it works. If somebody has an idea why this happens, obviously I'd like to hear from you.

Ran into a problem when installing Oracle Identity Management into a WLS 11g. Registering the OID with opmnctl gave me an oracle.as.config.ProvisionException. Solved it by extending the domain (although the configuration of the OID was specifically set to No Domain). Make sure that the Enterprise Manager is in the domain. After that (and this is the important part) make sure to restart the domain, at least the AdminServer.

This is an age old dilemma for people like me. You work in a project, that has several environments (DEV, TEST, QA, PRD). Typically as a project member you are not allowed access to QA and PRD - which is very good. The main problem is that the QA and PRD environments offer high availability. In order to provide a good installation manual you need to come up with clustering even when you do not have enough machines. So for my current project I have chosen a different approach. I have four blades, three with 1 CPU (dual core) and one with 2 CPU's (dual core as well). I use one for the database, one for the middle tier (the bigger one), one for the web tier, and the fourth one for the load balancer and firewall. The load balancer and firewall will be done with iptables and HAProxy. Now on the middle tier I needed to have 14 different nodes. I created virtual NIC's and put them into the hosts file as well. In order to have "independent" WebLogic Servers I installed them i...

I intended to install some WLS homes on Friday. Somehow, when I unchecked the "I want to receive security updates via My Oracle Support" I ended up with a grayed out dialog box. This wandered around my head the whole weekend. I retried this morning and found a solution. Please check out the document on http://www.foxglove-it.nl/html/documents.html (easier for me to put documents there, instead of blogspot.

It seems that I'm all into silent installs these days. Trying to do a WebLogic installation in silent mode. Went to the documentation, as a few things have changed since the early BEA days. So I found the sample file for the silent.xml . Without big thinking I copied the sample like this: &ltbea-installer&gt &ltinput-fields&gt &ltdata-value value="D:\Oracle\Middleware_Home" name="BEAHOME"&gt &ltdata-value value="D:\Oracle\Middleware_Home\wlserver_10.3" name="WLS_INSTALL_DIR"&gt &ltdata-value value="WebLogic Server/Core Application ServerWebLogic Server /Administration ConsoleWebLogic Server/Configuration Wizard and Upgrade FrameworkWebLogic Server/Web 2.0 HTTP Pub-Sub ServerWebLogic Server/WebLogic JDBC DriversWebLogic Server/Third Party JDBC DriversWebLogic Server /WebLogic Server ClientsWebLogic Server/WebLogic Web Server Plugins WebLogic Server/UDDI and Xquery SupportWebLogic Server/Server Example...

I need to install an Oracle IDM on a 64bit Linux. In order to get this running I need a 64bit WebLogic Server. As this is not delivered with an included JDK I downloaded the Sun 1.6 JDK for 64bit Linux systems. When I then tried to install the WLS I always received an "out of disk" error. The magic option to pass to the self-extracting WLS is the following: java -Djava.io.tmpdir=/apps/tmp -jar ./wls1032_generic.jar

As I am setting my first baby steps into the world of Weblogic I have to deal with things that might seem very easy for the experienced Weblogic gurus out there, but nevertheless I put my ranting on this blog. When you are faced with an issue in your Weblogic domain, there is apparently no tool to delete this domain. The only solution seems to be to remove the directory in which you have created this domain.