WLS 6.0 installation.

Hi there!
Could I install WLS 6.0 in the same machine where WLS5.1 is installed and
running.
I just want to make some test with the new version.
There are any problem I should know?
Thanks&Regards

You can safely install WLS 6.0 on the same machine. Make sure the servers are
listening on different
ports or if you have multiple IP's to your box, you can bind each server to a
specific IP.
Kumar
Mauricio Del Moral wrote:
Hi there!
Could I install WLS 6.0 in the same machine where WLS5.1 is installed and
running.
I just want to make some test with the new version.
There are any problem I should know?
Thanks&Regards

Similar Messages

No workshop installed with Solaris WLS 7.01 installer ..

Dear all !
I justed installed a fresh WLS 7.01
on a Solaris 2.7 box ..
and i faced the same problem
as I already had with the full
installer for wls 7.0 ..
Even if I click custom .. and
click on all three parts, means
also make the click for the workshop
I didn't get the workshop
installed .. what can I do to
get them installed ???
Thanks !
     Frank

Hi Wayne !
>>
$ ./platform701_solaris.bin -mode=console | tee screenoutput.txtI used now a fresh file .. just downloaded from bea ..
ls -l server701_solaris.bin-rwxr--r-- 1 xxx xxx 134964352 Oct 7 13:35 server701_solaris.bin*
And made the same command like you ..
As you could see here .. no workshop is
installed :
cd bea701b/weblogic700
/usr/<something>/bea701b/weblogic700
ls -ltotal 8
drwxr-xr-x 6 xxx xxx 512 Oct 7 13:46 common/
drwxr-xr-x 4 xxx xxx 512 Oct 7 13:47 samples/
drwxr-xr-x 6 xxx xxx 512 Oct 7 13:46 server/
drwxr-xr-x 2 xxx xxx 512 Oct 7 13:48 uninstall/
I attach you the whole conversation at the end ..
The question whihc are open :
a) Contains server701_solaris.bin the workshop yes or no
a1 ) if yes, why is he not installed
a2) if no .. is the webpage wrong , which states that
the workshop comes with the server .. and the
install routine say this too
b) Does the installer have problems if other bea-homes exist
on one system
Really strange the whole thing, isn't it ?!
Thanks for the help !
     Frank
BTW .. what you can see at the end ..
Congratulations! WebLogic Platform 7.0.1.0
has been successfully installed to
/usr/<something>/bea701b/weblogic700.
The installer does not reflect really what I'm doing ..
( I installed weblogic Server not weblogic platform .. )
------------- the install output -----------------------------------
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Welcome:
This installer will guide you through the installation of
WebLogic Platform 7.0.1.0. Type "Next" or enter to proceed to the
next prompt. If you want to change data entered previously,
type "Previous". You may quit the installer at any time by
typing "Exit".
Enter [Exit][Next]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Welcome:
This installer will guide you through the installation of
WebLogic Platform 7.0.1.0. Type "Next" or enter to proceed to the
next prompt. If you want to change data entered previously,
type "Previous". You may quit the installer at any time by
typing "Exit".
*** ERROR *** Invalid Entry: n
Enter [Exit][Next]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
BEA Systems License Agreement:
BEA SYSTEMS, INC. SOFTWARE LICENSE AGREEMENT
USE OF SOFTWARE ORDERED FROM BEA SYSTEMS, INC. ("BEA") IS PROVIDED ONLY
UNDER LICENSE FROM BEA. PLEASE READ THE FOLLOWING LICENSE CAREFULLY
AND INDICATE YOUR ACCEPTANCE BY CLICKING THE ACCEPTANCE BOX. CERTAIN
CAPITALIZED TERMS ARE DEFINED IN SECTION 11.
1. LICENSE TERMS
a. Evaluation Use. The terms of this Section 1(a) are applicable to you
if you have registered as an Evaluation customer. Subject to the terms
of this Agreement, BEA grants to you a non-exclusive,
non-transferable, license to use the evaluation version of the Software
solely for Evaluation Use. Third party software products or modules
supplied by BEA, if any, may be used solely with the Software. This
Enter [Yes][No][Exit][Previous][More]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
BEA Systems License Agreement:
BEA SYSTEMS, INC. SOFTWARE LICENSE AGREEMENT
USE OF SOFTWARE ORDERED FROM BEA SYSTEMS, INC. ("BEA") IS PROVIDED ONLY
UNDER LICENSE FROM BEA. PLEASE READ THE FOLLOWING LICENSE CAREFULLY
AND INDICATE YOUR ACCEPTANCE BY CLICKING THE ACCEPTANCE BOX. CERTAIN
CAPITALIZED TERMS ARE DEFINED IN SECTION 11.
1. LICENSE TERMS
a. Evaluation Use. The terms of this Section 1(a) are applicable to you
if you have registered as an Evaluation customer. Subject to the terms
of this Agreement, BEA grants to you a non-exclusive,
non-transferable, license to use the evaluation version of the Software
solely for Evaluation Use. Third party software products or modules
supplied by BEA, if any, may be used solely with the Software. This
*** ERROR *** Invalid Entry: Y
Enter [Yes][No][Exit][Previous][More]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Choose BEA Home Directory:
BEA home choice
1| Create a new BEA Home [usr/<something>/bea]
->2| Use an existing BEA Home [usr/<something>/java/oodbms/bea2]
Enter index number to select OR [Exit][Previous][Next]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Choose BEA Home Directory:
BEA Home = [usr/<something>/bea]
Input new BEA Home Directory OR [Exit][Previous][Next]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Choose BEA Home Directory:
BEA home choice
->1| Yes, Use this BEA home directory [usr/<something>/bea701b]
2| No, return to BEA home directory selection
Enter index number to select OR [Exit][Previous][Next]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Choose Install Type:
->1| Typical Installation (Install all software components, including
program files and examples.)
2| Custom Installation (Choose software components to install and
optionally create custom application domains. Recommended for advanced
users.)
Enter index number to select OR [Exit][Previous][Next]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Choose Components:
Release 7.0.1.0
|_____WebLogic Server [0] x
|_____Server [0.0] x
|_____Workshop [0.1] x
|_____Server Examples [0.2] x
Enter number exactly as it appears in brackets to toggle selection OR
[Exit][Previous][Next]>
<------------- BEA Installer - WebLogic Platform 7.0.1.0 ------------->
Choose Components:
->1| Yes, use these component selections
2| No, return to component selection
Enter index number to select OR [Exit][Previous][Next]>
<------------- WebLogic Platform Installer - WebLogic Platform 7.0.1.0
------------->
Choose Product Directory:
Product Installation Directory =
[usr/<something>/bea701b/weblogic700]
Input new Product Installation Directory OR [Exit][Previous][Next]>
<------------- WebLogic Platform Installer - WebLogic Platform 7.0.1.0
------------->
Choose Product Directory:
->1| Yes, use this product directory
[usr/<something>/bea701b/weblogic700]
2| No, select another product directory
Enter index number to select OR [Exit][Previous][Next]>
<------------- WebLogic Platform Installer - WebLogic Platform 7.0.1.0
------------->
Copying files..
0% 25% 50% 75% 100%
[------------|------------|------------|------------]
Copying JDK....
<------------- WebLogic Platform Installer - WebLogic Platform 7.0.1.0
------------->
Run Configuration Wizard
->1 - Yes, run Configuration Wizard to create my application domain
2 - No, skip Configuration Wizard
Enter index number to select OR [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Choose Domain Type
->1 - WLS Examples
2 - WLS Petstore
3 - WLS Domain
4 - WebLogic Workshop
Enter a number or [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Choose Server Type
->1 - Single Server (Standalone Server)
2 - Admin Server with Managed Server(s)
3 - Admin Server with Clustered Managed Server(s)
4 - Managed Server (with owning Admin Server configuration)
Enter a number or [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Choose Domain Name
1 - Modify current selection(workshopDomain)
->2 - Use current name
Enter a number or [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Configure Single Server
1- Modify Server Name (myServer)
2- Modify Server Listen Address ()
3- Modify Server Listen Port (7001)
4- Modify Server SSL Listen Port (7002)
Enter a number or [Exit][Previous][Next]>
Enter Server Name or [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Configure Single Server
1- Modify Server Name (fraServer)
2- Modify Server Listen Address ()
3- Modify Server Listen Port (7001)
4- Modify Server SSL Listen Port (7002)
Enter a number or [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Choose Location to Create Domain
1 - Modify current selection
     (/usr/<something>/bea701b/user_projects)
->2 - Use current directory
The domain directory will be located at:
     (/usr/<something>/bea701b/user_projects/workshopDomain)
Enter a number or [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Enter User Name or [Exit][Previous][Next]>
Enter Password or [Exit][Previous][Next]>
Enter Verify Password or [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Configuration Summary
Domain Name: workshopDomain
Server Type: Single Server (Standalone Server)
Domain Template Name: WebLogic Workshop
Install Directory:
/usr/<something>/bea701b/user_projects/workshopDomain
Listen Address: localhost and primary IP address
Listen Port: 7001
SSL Listen Port: 7002
User Name: system
Password: ********
Enter [Exit][Previous][Create]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Domain Configuration Wizard has successfully created "workshopDomain"
domain
Enter [Exit][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Configuration Wizard Complete
1 - Run Configuration Wizard again.
->2 - End Configuration Wizard.
Enter [Exit][Previous][Next]>
<------------- BEA Configuration Wizard - WebLogic Platform 7.0.1.0
------------->
Install Complete
Congratulations! WebLogic Platform 7.0.1.0
has been successfully installed to
/usr/<something>/bea701b/weblogic700.
Press any key to continue OR [Exit]>

JDK 7 + Red Hat 6 64-bit = WLS 10.3.6 and WLS 12.1 installer not working

Hi,
I have installed Weblogic 10.3.6 and 12.1 on two different Red Hat 6 64-bit servers. I started out using JDK 7 (1.7.0_05) but when I reached the screen where you select which products to install I could not select or deselect anything with the mouse. On others I could not use the keyboard for input. As soon as I switched to JDK 6 everything worked fine.
As a workaround I installed and configured everything with JDK 6 and switched to JDK 7. This works fine and the developers are happy.
But I have discovered that the I have the same problem when I use config.sh, so it is general problem with the GUI and JDK 7.
I opened a Service Request on MOS in June but I don't think the support guy has much of a clue. He has been testing with Windows. His last suggestion was running the installer with -d64, but according to the manual this should only be used when using a 32/64-bit hybrid JDK, which is not the case.
Anybody has any ideas?
Regards Peter

Hi Peter,
I check the SR well I think it not so see to reproduce in other environment.
But we can instead to engineer to reproduce on their environment.
But as of I would suggest to use command line or silent mode to install wls.
Going through GUI will have many complex issue on OS to OS base so best practice is to have such installation using command line or silent modes.
Note: If engineer is unable to reproduce such issue in their environment then Oracle will not consider that is BUG then there would be issue in your environment only.
Regards,
Kal

WLS 32-bit installer on a 64-bit JVM

Hi All,
I was also told that I could run the WLS 10.3.1 (32 bit) installer wls1031_solaris32.bin along with a 64-bit JVM and WebLogic will run in 64-bit mode. Is that true?
If yes then what is the need for a 64 bit installer?
My underlying OS is solaris 64 bit.
I wonder how is that possible. Can anyone help me understand?
Thanks in advance.

It doesn't make sense to me that a 32-bit installer is installing a 64-bit JVM unless that installer will install both 32-bit and 64-bit JVMs.
I would suggest you use the installer from the edelivery site: WebLogic Server 9.2 MP3 Sun Solaris SPARC (64-bit) V15433-01 598M.
Regards,
John A. Booth
http://www.metavero.com

Why does WLS 9.2 installer say "Insufficient disk space!" on OS X w/122GB?

hi all,
i just installed mac os x 10.4.0 about 4 days ago onto a brand new 160 GB internal hdd. apart from some upgrades (10.4.9, java 1.5, xcode docs, etc.) the only other apps i've installed are eclipse 3.2 development ide & mozilla. that left me with 122 GB available on my hdd (as reported by "Get Info").
today, i tried to install BEA WebLogic Server 9.2 MP1 (the ibm aix generic installer). the installer for wls 9.2 comes as an executable jar file that must be executed from the shell. i executed the following command in the shell:
$ java -jar server921_generic.jar -log=/Users/myhome/logs/wls92_mp1_install_02_05_07.logthe installer gui loads, prompts me for the license agreement, some install folder locations (i told it to install to "/Users/myhome/development/bea"), etc. then, it reports:
<blockquote>
"Insufficient disk space! The installer requires: 5MB for the BEA Home at /Users/myhome/development/bea and 270 MB temporary work space at /tmp/bea30536.tmp. There is only 271MB available at /."
</blockquote>
ONLY 271MB AVAILABLE!!? how can that be?
so, i tried directing it to install to "/Applications/bea". i also started the installer with an option to use "/Applications/tmp" (which i created with mkdir) as an alternate tmp directory. this time with "sudo" - just in case:
$ sudo java -Djava.io.tmpdir=/Applications/tmp -jar server921_generic.jar -log=/Users/myhome/logs/wls92_mp1_install_02_05_07.logthis time its:
<blockquote>
"Insufficient disk space! The installer requires: 5MB for the BEA Home at /Applications/bea and 270 MB temporary work space at /Applications/tmp/bea30537.tmp. There is only 271MB available at /."
</blockquote>
what gives? on my solaris box, i can do "growfs" to expand the space available to a filesystem. is there some way i can do something similar on os x? or is there ANYTHING else to give "/" access to more of the 122 GB hdd space that is obviously available?
thanks in advance for your help.

hi,
please take a look at "[url http://forums.bea.com/bea//thread.jspa?threadID=400003593&tstart=15&mod=1178464358368]HELP: Which command line args to launch Workshop 9.2 on Mac OS X 10.4?"
to summarize that thread: the generic installer does not come with workshop 9.2 or portal 9.2 because they are not supported on aix, hp or mac os x. weblogic server is not supported on max os x at all.
that thread also explains how i was able to get workshop 9.2 installed and running on os x:
"...i happen to have a working installation of wls & wlw
on my sun microsystem's sunblade 100 with solaris 9
(installed using bea's solaris_sparc-specific .bin
installer; which _does_ come bundled with the wlw ide).
so, i copied the wlw-related stuff (everything in
$bea_home/workshop92 & everything in
$bea_home/common/eclipse) from my solaris box to the
appropriate folders on my mac..."if you have (or can get access to) a working installation
of workshop that has already been installed on another
supported os, then you'll need to copy the
workshop-related stuff from the supported os to your mac;
like i described in the above thread. you'll need to keep
in mind that there are some os-specific plugins that come
with the supported versions of workshop; you will need to
replace those with their mac-specific equivalents.
if you click on my username in the top left-hand corner of
this post, you will get a list of posts i've made recently
that detail my experiences getting weblogic server 9.2 and
workshop 9.2 installed on mac os x. if you can
follow along with the info in those threads, you will
learn everything that i know about the subject. good luck.
let us know how you get on?

Why might WLS 9.2 installer say "Insufficient disk space!" on OS X w/122GB?

hi all,
i just installed tiger about a week ago onto a brand new 128 GB internal hdd. apart from some upgrades (10.4.9, java 1.5, xcode docs, etc.) the only other apps i've installed are eclipse 3.2 development ide & mozilla. that left me with 122 GB available on my hdd (as reported by "Get Info").
today, i tried to install BEA WebLogic Server 9.2 (a j2ee application server). the installer for wls 9.2 comes as an executable jar file that must be executed from the shell. i executed the following command in the shell:
$ java -jar server921_generic.jar -log=/myhome/logs/wls92mp1_install_02_0507.log
the installer gui loads, prompts me for the license agreement, some install folder locations (i told it to install to "/Users/myhome/development/bea"), etc. then, it reports:
"Insufficient disk space! The installer requires: 5MB for the BEA Home at /Users/myhome/development/bea and 270 MB temporary work space at /tmp/bea30536.tmp. There is only 271MB available at /."
ONLY 271MB AVAILABLE!!? how can that be?
so, i tried directing it to install to "/Applications/bea". i also started the installer with an option to use "/Applications/tmp" (which i created with mkdir) as an alternate tmp directory. this time with "sudo" - just in case:
$ sudo java -Djava.io.tmpdir=/Applications/tmp -jar server921_generic.jar -log=/myhome/logs/wls92mp1_install_02_0507.log
this time its:
"Insufficient disk space! The installer requires: 5MB for the BEA Home at /Applications/bea and 270 MB temporary work space at /Applications/tmp/bea30537.tmp. There is only 271MB available at /."
what gives? on my solaris box, i can do "growfs" to expand the space available to a filesystem. is there some way i can do something similar on os x? or is there ANYTHING else to give "/" access to more of the 122 GB hdd space that is obviously available?
thanks in advance for your help.
p.s. there are no disk quotas or anything like that:
$ sudo quota
Disk quotas for user root (uid 0): none
$ quota
Disk quotas for user me (uid 501): none
i also ran repair permissions, just in case. same difference.
Message was edited by: l'il john l'concharoo

found my answer!: java -Dos.name=unix ...

WLS (40-bit) to WLS (128 bit) installation

Hopefully this will help shed some light on the subject.
Terry
If you receive the following warning:
<I> <Security> WARNING: Exportable (weak) WebLogic Server build running and
domestic (full) strength SSL license detected. Only exportable strength SSL
connections will be accepted.
This indicates that you have a full strength certificate but a weak strength
build of the server. For full strength encryption there is a different WLS
build. The generally-available (weak/40-bit) version of WLS 5. 1 supports
512-bit certificates and 40-bit bulk data encryption. The full strength
(128-bit) WLS 5.1 build supports 768-bit and 1024-bit certificates and
128-bit bulk data encryption. Your sales contact can provide the required
forms and a special URL to download the full strength build of WebLogic.
The installation for the 128-bit version is the same as the installation for
the 40-bit version. When converting to the 128-bit version a complete
re-installation is necessary. If you are installing service packs, please
note that although Service Packs 1-5 are the same for both the 40-bit and
128-bit versions, SP6 for the 128-bit version is a controlled release. In
order to obtain SP6 for WLS 5.1 (128-bit), you will need to contact your
sales representative who will be able to provide a URL where it can be
downloaded.
Some other notes concerning the 128-bit installation. First, ensure that
you are using the permanent license that has been updated with the 128-bit
key. Second, for information on setting up WLS SSL (i.e. installing
1024-bit security certificates), please see the documentation at:
http://www.weblogic.com/docs51/classdocs/API_secure.html.
It is my understanding that the difference between the 40-bit and 128-bit
versions of WLS 5.1 is in the encryption/decryption module. Since the
difference is limited to this particular module, transitioning from the
40-bit to the 128-bit version should be transparent as far as WLCS (3.1.1
SP1 & 2.01 SP2) is concerned. This is supported by the fact that there is a
single version of WLCS for both domestic use and export use.
A couple of general notes concerning WLCS 3.1.1/2.0.1 installations running
on top of WLS 5.1 (40-bit or 128-bit) SP6:
WLCS 3.1.1: To date, support cases have not been received with a WLCS
3.1.1 installation running on top of WLS
5.1 (40-bit/128-bit) SP6 where SP6 has been determined to be the
problem.
WLCS 2.0.1: With one minor exception (see Solution S-05838 below),
support cases have not been received with a
WLCS 2.0.1 installation running on top of WLS 5.1 (40-bit/128-bit) SP6
where SP6 has been determined to be the
problem.
A couple of general notes concerning WLCS 2.01 and WLS 5.01 (40- or 128-bit)
Service Packs 1-6:
- There have been problems when using SP1, SP2 and SP3 for WLS 5.
- Therefore, SP4 (minimum) is required.
- To date, support cases have not been received where SP5 has been
determined to be a problem.
- There is one small issue related to SP6 (see Solution S-05838 below).
Otherwise, support cases have not been
received where SP6 has been determined to be a problem.
- Following the SP6 installation, all the JSPs will need to be
recompiled. Due to the custom tags used in WLCS 2.0.1,
the JSPs cannot be pre-compiled. Therefore, recompiling will occur as
the pages are accessed.
Please see the release notes that accompany each service pack downloads for
issues that are resolved with each particular
service pack.
Solution S-05838
A better solution to the problem: WLCS 2.0.1 only: DataLoader script causes
ASCClientException with WLS 5.1 SP6
Old Solution:
Use WLS 5.1 SP5 to run the DataLoader, THEN upgrade to SP6.
New Solution:
You can run the DataLoader without exceptions for WLCS 2.0.1 SP2 and WLS 5.1
SP6 if you modify the script to use t3 socket connections instead of http.
Open the DataLoader script for editing and change the two appearances of
"http://" to "t3://".

You need to contact your sales rep and get the domestic strength version of
WLS.
Michael Girdley
Product Manager, WebLogic Server
BEA Systems Inc.
Ravi Kumar.T <[email protected]> wrote in message
news:8945ju$lu8$[email protected]..
Where to specify the no of bits for encryption for SSL. Is it depend on
verisign certificates installed!!
We are using we weblogic 4.5.1 on Solaris. and my site is having following
encryption
SSL 3.0, RC4 with 40 bit encryption (Low); RSA with 512 bit exchange
and I have seen some other sites are having
SSL 3.0, RC4 with 128 bit encryption (High); RSA with 1024 bit exchange
thanks..
ravi

WLS 7.0 installation problem on HP-UX 11

When I try to start the net installer net_platform700_hpux.bin on our HP machine,
it throws the following error:
End-of-central-directory signature not found.
** Error during init, error code = 2.
Any help will be appreciated.
Thanks,
Ayan

Ayan,
I did a quick search on the error you posted - I found that most times the problem is
that the .zip file has been corrupted. Maybe you should try the download again.
Regards,
Glenn Dougherty
Developer Relations Engineer
BEA Technical Support
Ayan wrote:
When I try to start the net installer net_platform700_hpux.bin on our HP machine,
it throws the following error:
End-of-central-directory signature not found.
** Error during init, error code = 2.
Any help will be appreciated.
Thanks,
Ayan

Co-existing 5.1 and 6.1 WLS installations?

We have a need to temporarily have a new WLS 6.1 installation running simultaneously on the same server as an existing WLS 5.1 installation. Anyone know of any reason this wouldn't work, assuming of course they're set to listen/talk to different ports? Are there any other dependencies?

Hi.
be sure to install in separate directory trees (obviously). Other than that you should be fine. The only other reason this wouldn't work is if you don't have enough system ram to accomodate both servers. FWIW I have done this several times myself.
Regards,
Michael
Mason Jones wrote:
We have a need to temporarily have a new WLS 6.1 installation running simultaneously on the same server as an existing WLS 5.1 installation. Anyone know of any reason this wouldn't work, assuming of course they're set to listen/talk to different ports? Are there any other dependencies?--
Michael Young
Developer Relations Engineer
BEA Support

WebLogic Server 9.2.2 & running WLS 9.1 generated WLST config.py

Hello everybody,
I am running a WLS 9.1 WLST ConfigToScript config.py in a blank new WLS 9.2 installation to recreate a WLS Server domain.
The original script generated reflects the Administration Server residing on one machine while the Application Server, applications, and node manager reside on another machine. I've edited the script for the new target machine. In this case they want to everything to reside in a single Solaris 10 Zone. The Administration Server resides on one virtual IP address while the nodemanger, application server, and applications all reside on another virtual IP address. Both these addresses are defined in the zone, which has it's own IP address in which WLS 9.2 is installed.
When the script runs it tries to connect to the Administration Server I've defined and when it fails to connect it proceeds to create a brand new administration server. This proceeds as expected and finally when WLST attempts to connect to the now running Administration Server I get the following errors:
WLST-WLS-1207767457017: <Apr 9, 2008 2:58:49 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
WLST-WLS-1207767457017: <Apr 9, 2008 2:58:49 PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Server started successfully.
Started Server. Trying to connect to the server ...
Connecting to t3://10.99.99.99:8082 with userid system ...
WLST-WLS-1207767457017: Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
WLST-WLS-1207767457017: Exception in thread "Timer-1" java.lang.OutOfMemoryError: PermGen space
WLST-WLS-1207767457017: Exception in thread "[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
I've tried adding "-XX:MaxPermSize=256m" when I invoke java to run WLST but of course after I got the error again I realized that it is the newly created WLS Administration Server that is getting this error.
I would have thought the WLST configToScript would have exported any special JVM flags used by the original Administration Server, nodemangers, and such.
Could you please explain how I fix this?
Do I need to lookup in the original 9.1 environment all of these JVM flags and integrate them somehow in the ConfigToScript config.py script?
Thanks very much.

Try changing the config.py script:
And server for the line "startServer", and there add that MaxPermSize.
For example:
startServer("AdminServer", "Domain", t3://XXXX, "weblogic","weblogic","/opt/BEA/user_projects/domains/Domain", timeout=90000, jvmArgs='-XX:MaxPermSize=256m, -Xms512m, -Xmx512m')
Schelstraete Bart
[email protected]
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst

Does WLS 9.0 jms ra support JCA 1.5?

WLS 9.0 installation incudes jms-xa-adp.rar, jms-notran-adp.rar, jms-local-adp.rar. But all support only JCA 1.0 version if you look at their resource adapter descriptors. The release note says that WLS 9.0 supports JCA 1.5, does not say anything about JMS RA.
Does WLS 9.0 JMS RAR support JCA 1.5? If so, where can I
get these rars?
Thank you in advance
Charles

desuported? Can you post a source for this?
9.0.4 is not certified with JDK 1.5 and will not be. AS 10.1.3 is the first release that is (as far as I know).

WLS Zip distribution and Fusion Middleware Control components

i am working with a WLS Zip distribution installation and i'm not seeing opmnctl or any reference to the Fusion Middleware Control that i need to install Oralce Webforms.
what components install do we need to get this install up to speed?
thanks.

Hi,
   WLS ZIP distribution is only intended to be used for only developers.
   As per your requirement in order to install Oracle Forms you need to install .jar or .exe or .bin file depending upon you OS.
   Then install Oracle Forms 11g.
   So request to follow the below steps if your OS is a 64 bit :-
1)Download and Install JDK 1.6.0_XXX from the below URL :-
   Java Archive Downloads - Java SE 6
2)Download and Install Weblogic 10.3.6 which is certified with Forms and Reports 11.1.2.2.0 or Forms 11.1.1.7.0 which could be downloaded from the below URL :-
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
   Section :- Oracle WebLogic Server 11gR1 (10.3.6) + Coherence - Package Installer
   In order to install Weblogic set you java path to point to the JDK 1.6.0_xxxx then run the below command :-
   java -jar wls1036_generic.jar [ If the OS is 64 bit ]
3) Download Forms and Reports 11.1.2.2.0 or Forms 11.1.1.7.0 from the below URL 's :-
   Forms Downloads</title><meta name="Title" content="Forms Downloads"><meta name="…
    Incase if your OS is 32 bit then download the .bin or .exe file for Weblogic from the above URL's and also the respective Forms binary.
Regards,
Prakash.

[WLS 9.2] Intermittent performance glitch creating InitialContext

Hi,
We are experiencing a peculiar problem with our WLS 9.2 installations: the time taken to create an InitialContext on a remote host has extremely variable performance.
The setup is that we have a gateway server running WLS 9.2 on Solaris 10 that is sends JMS messages to a number of application servers (all running WLS 9.2/Solaris 10). This is done, in the usual fashion, by creating an InitialContext from which we can lookup the ConnectionFactory and Queue. The gateway server is very sensitive to delays in sending the JMS message and any message that cannot be delivered within a specified time triggers a failover scenario and the message is routed to another server.
Investigation of the what was causing the failover to trigger showed that it is that the creating of the InitialContext that occassionally takes significantly longer than we expected. We set up a simple test in isolation to our system that schedules a task every 30 seconds that only creates an InitialContext and times how long it takes. Here are the stats from two sample runs:
Run 1
Mean: 13 ms
Average: 55.54 ms
Min: 11ms
Max: 5086 ms (5 s)
Sample size: 1566
Run 2
Mean: 22 ms
Avgerage: 139.7 ms
Min: 14 ms
Max: 11444 ms (11 s)
Sample size: 1733
Interestingly, when we run this same test from a Windows-based WLS 9.2 installation, the time reported by the test is 0 ms. I can only assume that there is an underlying
We are working around the problem by creating a pool of message dispatchers that already have an initialised InitialContext but we still run into this problem when the pool needs to grow and additional dispatchers are created.
A smaller scale test on using a Windows-based gateway connection to the same Solaris-based application server did not experience the sample problem.
Any ideas?
The code used for the test:
public class InitialContextTest implements Runnable {
    private static final Logger LOG = Logger.getAnonymousLogger();
    private Hashtable<String, String> _environment = new Hashtable<String, String>();
    public void run() {
        final long start = System.currentTimeMillis();
        weblogic.security.Security.runAs(new Subject(), new PrivilegedAction<Void>() {
            public Void run() {
                InitialContext context = null;
                try {
                    context = new InitialContext(_environment);
                } catch (NamingException e) {
                    LOG.log(Level.SEVERE, "test: Cannot create initial context", e);
                } finally {
                    try {
                        if (context != null) {
                            LOG.log(Level.INFO, "test: Closing initial context");
                            context.close();
                    } catch (NamingException e) {
                        LOG.log(Level.SEVERE, "test: Cannot close initial context", e);
                return null;
        final long end = System.currentTimeMillis();
        LOG.log(Level.INFO, "test: t=" + (end - start));
    public void setEnvironment(Map<String, String> environment) {
        _environment.putAll(environment);
}Edited by: Marcus Edwards on Oct 16, 2009 5:16 PM
remove standard deviation figures at they are invalid

Hi,
I don't know what the issue is, but I imagine there could be any number of causes. Overwhelmed DNS servers, network issues, or a even a very long GC. Or there could be a competing process somewhere local or remote that consuming 100% CPU intermittently (which would freeze out or slow other work).
In case you don't already know:
1 - Contexts are thread safe.
2 -There's usually no need to have multiple contexts if they all resolve to the same remote JNDI host, or even the same cluster (usually no performance benefit).
3 - Multiple WebLogic Java contexts on a local JMS that all connect to the same remote JVM will all multiplex over the same socket. When a new context is created, WebLogic sets up a new network connection, checks to see if the local JVM already is talking to the same server (by comparing data returned from the new connection to data from current connections), and, if so, tears down the new network connection and routes traffic for the new Context over the old pre-existing connection.
4 - As you've already discovered, its best practice to cache contexts. In addition, it's best practice to cache JNDI lookup results, as well as JMS connections, sessions, producer, and consumers.
5 - The test you posted below has a memory leak: it should call context.close() when its done with the context.
Tom

Cluster setup

          Hi,
          I'm running two WLS 6 in a multihomed machine. Do I need to install to instances
          of WLS or can I install one instance and use the same file, but starting with
          different scripts. Are there any negatives or positives about using one install,
          but two scripts? These instances will be clustered.
          Thanks for your help.


          But do I have to have the same installation or I can have different
          installations?
          Should the clusters use the same config.xml files?
          Also, am I correct to assume that the admin server can also be a cluster?
          I have only two machines and I want one of them to be the admin, as well as
          to be one of the nodes in the cluster. Is there anything wrong with this
          configuration?
          Thanks.
          Andre Mendonca
          [email protected]
          "Kaye Wilcox" <[email protected]> wrote in message
          news:[email protected]...
          > You'll need to create your cluster and add your server instances to the
          > cluster via the console (see
          > http://edocs.bea.com/wls/docs60/adminguide/config.html#1024476).
          >
          > You'll need only one WLS 6.0 installation on your machine. You will need a
          > start up script for each server instance that you want to boot up. So if
          you have
          > an admin server and a cluster of two managed servers you will need three
          start up
          > scripts for your servers (see
          <WL_HOME>/wlserver6.0/config/mydomain/startWebLogic.sh
          >
          > and startManagedWebLogic.sh for example start up scripts).
          >
          > wwen wrote:
          >
          > > Hi,
          > >
          > > I'm running two WLS 6 in a multihomed machine. Do I need to install to
          instances
          > > of WLS or can I install one instance and use the same file, but starting
          with
          > > different scripts. Are there any negatives or positives about using one
          install,
          > > but two scripts? These instances will be clustered.
          > >
          > > Thanks for your help.
          >

Is it possible to install ODSI 10.3g as a web application via a WAR or EAR?

I only know how to install it from the single .exe that installs WebLogic and ODSI in one shot. My customer has an automated process for rolling out WebLogic servers and would like to know if ODSI can be installed from an EAR or WAR. Does anyone here know if that's possible? Have any hints on where to start looking for something like this?
Thanks.
Edited by: user10592709 on Oct 6, 2009 12:28 PM

It is difficult to respond to questions that ask how to implement a specific (impossible) solution, rather than ask how to fulfill a particular requirement (scripted install). Please visit the "How to Ask a Question" announcement in this forum if you want more on that.
ODSI does not specify how it is implemented (war, ear, extension to WLS), and therefore there is no documentation on the subject.
For installation options, please refer to the installer documentation. I suspect there is no documentation describing how to install ODSI without using the installer.
Is there some reason they are not using the silent installer and then a template? ( "Because they have built their own Opsware installer" is not an acceptable answer)
How does the Opsware installer work? If it leverages the WLS silent installer, then it seems obvious that changing it to leverage the WLS+ODSI silent installer would work. If it uses a zipped-up WLS installation (or template), then it seems obvious that changing it to leverage a zipped-up WLS+ODSI installation would work. There really aren't any other possibilities, are there?
It seems unlikely that Opsware scripts that install WLS would somehow start installing WLS+ODSI without being modified. I don't know why there is any expectation that they would. I don't know why there is resistance to modifying the scripts. These are really customer questions - not ODSI questions.
There is nothing stopping you or your customer from installing WLS, then installing WLS+ODSI beside it, then doing a 'diff', and then scripting the changes. Except maybe that the WLS+ODSI installer already does this, and then you wasted your time building something that already exists.

WLS 6.0 installation.

Similar Messages

Maybe you are looking for