Cloning PCs with a WebLogic Install

[Tom_Davidson]

All,

In the past we have made an image of our developer workstation (includes VS, Oracle, patches, E1, etc). Then when we need to create a new fat client, or 'fix' a broken one, we simply use the image and have the developer take the latest full package (and updates).

With the advent of 9.2 OAS is no longer supported, and a WebLogic install is required before the developer can use the local web. Has anyone created a WebLogic install for a similar situation, what things should I look out for?

Tom

 

[altquark]

Weblogic needs the nodemanager to tie into the DNS Name of the client. So it might be tricky to do this. You might have to create the VM without weblogic, then install weblogic first, then install the E1 client. That might be the fastest way, though it slows you down a little.

 

[Tom_Davidson]

John, That is my fallback, I am hoping someone out there smarter than me, has figured out how to do this already. Something like using localhost, I'm spread thin at the moment and just don't have the time to do this at the moment.

Tom

 

[A.J.deWit]

Done this recently a few times. This should be no problem, we cloned our VMs after having installed JDE Client and all other required products like:
- Adobe
- Visual Studio
- Oracle Client (disable datapump)
- JDK
- Weblogic Server
- E1LOcal
- JDE Full Package (+ WebDev feature)
- set ini's (jas/jde)

When the Fat Client is working correctly you can clone, after cloning you only need to set the Oracle E1LOCAL listener settings.

Change the listener.ora in the oracle base folder where you installed EnterpriseOne Database Engine:
[OracleBase]\oracle\E1Local\NETWORK\ADMIN

Change the hostname after "HOST = " to reflect the Fat Clients name in the LISTENER section.

That worked for me.

 

[paul_ross]

All,

In the past we have made an image of our developer workstation (includes VS, Oracle, patches, E1, etc). Then when we need to create a new fat client, or 'fix' a broken one, we simply use the image and have the developer take the latest full package (and updates).

With the advent of 9.2 OAS is no longer supported, and a WebLogic install is required before the developer can use the local web. Has anyone created a WebLogic install for a similar situation, what things should I look out for?

Tom

Tom,

Did you actually give this a try? I am pretty sure I did this on a 9.2 install, but I do not recall if Weblogic was part of the image. Sorry, my memory is not what it used to be. You definitely have to update the Oracle listener, but I seem to recall that everything else worked fine. I would give it a try since it is pretty easy to clone a workstation.

 

[Soumen]

So the local web has 2 steps for installation.

1. Installing the WebLogic Standard (no domain configured)
2. Take the WLSH4A installation which takes care of the domain creation etc.

How about you create an image with a FAT client which has only step 1 completed, meaning only WebLogic installed. Thereafter you have the developer take the latest full package and install the WLSH4A setup which will take care of the Local Web.

 

[Tom_Davidson]

Paul, Actually doing this is tomorrows project. I'm hoping to skip a few dead ends by asking before I actually do it.
Soumen, This sounds like a promising idea. I'll give it a try.

Tom

 

[gRUttal1]

Newly created domains are always created in Development mode. And although full support for WebLogic on JRockit VE is only provided when running in Production mode, you may want to experiment with the product while using Development mode, which allows you to, for example, use the autodeploy feature. You can change the domain to Production mode using the Administration Console or WLST. Production mode is enabled in the console in the domain configuration section. For more information, see "Development vs. Production Mode Default Tuning Values" in Performance and Tuning for Oracle WebLogic Server.