I downloaded the files from OTN with following names:
win64_11gR2_database_1of2.zip
win64_11gR2_database_2of2.zip
Extracted both into the SAME directory with these names
C:\Oracle\Disk1
C:\Oracle\Disk2
Started the installation from C:\Oracle\Disk1\database\setup.exe
And the Installation failed due to file not found of {C:\app\11g\product\11.2.0\dbhome_1\oc4j\j2ee\oc4j_applications\WFMLRSVCApp.ear and some other files too}
I went through the http://download.oracle.com/docs/cd/E11882_01/install.112/e10843/toc.htm but there was nothing which mentioned where or how to rename the directories.
All my downloaded files were in the same directory but still I was facing the problem.
As both zip files contained database folder so I couldn't override the files.
I solved the file not found issue by coping all the folders under C:\Oracle\Disk2\database\stage\Components to C:\Oracle\Disk1\database\stage\Components
After restarting the installation it went like a charm and without any issues.
Thanks,
Venkata Sarvabatla
Technical Blog about Weblogic Portal,Webcenter,BPM and SOA Suite,Spring Framework issues and solutions - for Beginners, Intermediate professionals. In feature we will make it for Advanced level professionals also.
Monday, August 15, 2011
Friday, August 12, 2011
administrator password reset procedure in weblogic
hi,
I have followed the following steps on WLS 11g and I was able to start the AdminServer with new username/password.
Steps:
1: open a command prompt.
2: go to the %BEA_HOME%/user_projects/domains/base_domain/bin dir
cd %BEA_HOME%/user_projects/domains/base_domain/bin
3: run the setDomainEnv.cmd file.
4: This will bring you to base_domain dir. Now run the following command:
java weblogic.security.utils.AdminAccount weblogic welcome1 .
Do not forget to use the last "." which is going to inform the utility to create the DefaultAuthenticatorInit.ldift in the Domain_Home dir.
5: Also try to use a password with atleast 8 chars and with at least one numeric digit.
6: then rename the DefaultAuthenticatorInit.ldift that is already present in the %Domain_Home %/security dir to
DefaultAuthenticatorInit_old.ldift and place the newly generated DefaultAuthenticatorInit.ldift file in the %Domain_Home %/security dir.
7: Also delete the %Domain_Home %/servers/AdminServer/security/boot.properties file.
8: Rename the %Domain_Home %/servers/AdminServer/data/ldap/DefaultAuthenticatormyrealmInit.initialized file to DefaultAuthenticatormyrealmInit_old.initialized
9: Now you can try to start the Admin Server with through the command prompt using startWeblogic.cmd file.
Let me know if this resolves the issue or not.
I have followed the following steps on WLS 11g and I was able to start the AdminServer with new username/password.
Steps:
1: open a command prompt.
2: go to the %BEA_HOME%/user_projects/domains/base_domain/bin dir
cd %BEA_HOME%/user_projects/domains/base_domain/bin
3: run the setDomainEnv.cmd file.
4: This will bring you to base_domain dir. Now run the following command:
java weblogic.security.utils.AdminAccount weblogic welcome1 .
Do not forget to use the last "." which is going to inform the utility to create the DefaultAuthenticatorInit.ldift in the Domain_Home dir.
5: Also try to use a password with atleast 8 chars and with at least one numeric digit.
6: then rename the DefaultAuthenticatorInit.ldift that is already present in the %Domain_Home %/security dir to
DefaultAuthenticatorInit_old.ldift and place the newly generated DefaultAuthenticatorInit.ldift file in the %Domain_Home %/security dir.
7: Also delete the %Domain_Home %/servers/AdminServer/security/boot.properties file.
8: Rename the %Domain_Home %/servers/AdminServer/data/ldap/DefaultAuthenticatormyrealmInit.initialized file to DefaultAuthenticatormyrealmInit_old.initialized
9: Now you can try to start the Admin Server with through the command prompt using startWeblogic.cmd file.
Let me know if this resolves the issue or not.
Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine.
Error :
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Answer :
Cause of the error is : Heap size is larger than your computer's physical memory.
try with the below heap sizes
set DEFAULT_MEM_ARGS=-Xms1024m -Xmx1024m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m
if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=256m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
see the below link also :
http://javahowto.blogspot.com/2006/06/6-common-errors-in-setting-java-heap.html
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Answer :
Cause of the error is : Heap size is larger than your computer's physical memory.
try with the below heap sizes
set DEFAULT_MEM_ARGS=-Xms1024m -Xmx1024m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m
if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=256m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
see the below link also :
http://javahowto.blogspot.com/2006/06/6-common-errors-in-setting-java-heap.html
Wednesday, August 10, 2011
Difference between JSR 168 and JSR 286 portlets
Java Portlet spefication168 (v1.0) has very basic portlet porgramming model and had lot of limitations for portlet development. Java Portlet spefication286 (v2.0) was developed to overcome the shortcomings on v1.0 specs(JSR 168) such as:
1. Inter portlet communicaiton (IPC) - IPC through events and public render parameters
2. Support for WSRP 2.0
3. Public render paremeters - Allows portlets to share parameters with other portlets.
4. Portlet filters and listeners.
5. Resource serving - Provide ability for portlets to server a resource
6. AJAX support
Subscribe to:
Posts (Atom)