Starting Weblogic Server & Managed Server without password

You can use boot.properties file for starting without typing username password.

Please avoide blank lines in boot.properties file.

The clear text username and password will be encrypted the first time Weblogic server has been started.

Weblogic Server / Admin Server cd ${DOMAIN_HOME}/servers/AdminServer/security #pwd /u01/app/bihome/user_projects/domains/bifoundation_domain/servers/AdminServer/security echo username=weblogic > boot.properties echo password=******>>boot.properties nohup ${DOMAIN_HOME}/bin/startWebLogic.sh >> Adminserver.log 2>&1 & tail -f Adminserver.log

Managed Server cd ${MW_HOME}/user_projects/domains/bifoundation_domain/servers/bi_server1/security #pwd /u01/app/bihome/user_projects/domains/bifoundation_domain/servers/bi_server1/security echo username=weblogic > boot.properties echo password=******>>boot.properties cd $DOMAIN_HOME nohup ${DOMAIN_HOME}/bin/ startManagedWebLogic.sh >> ManagedServer.log 2>&1 & tail -f ManagedServer.log

Moreover You can use environment variable:

export JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.username=weblogic -Dweblogic.management.password=******"

Read more : http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/10g/r3/installconfig/enable_auto_login/boot_identity_file.htm#o

Start Oracle BI startNodeManager.sh has error "Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5"

Hi all,

Today after I have installed Oracle BI, I restart BI application server. To start BI Application server we have to perform 2 step as below:
1) source Environment variable:
. /u01/app/bihome/wlserver_10.3/common/bin/commEnv.sh
. /u01/app/bihome/user_projects/domains/bifoundation_domain/bin/setDomainEnv.sh
. /u01/app/bihome/user_projects/domains/bifoundation_domain/bin/setOBIDomainEnv.sh

2) start BI server:
  i> nohup sh ${DOMAIN_HOME}/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=123456 > log_WL.out &
  ii> nohup sh ${WL_HOME}/server/bin/startNodeManager.sh > log_NOD.out &
  iii> nohup sh ${DOMAIN_HOME}/bin/startManagedWebLogic.sh bi_server1 t3://biapp.mylab.com:7001 > log_MWL.out &
  iv> ${MW_HOME}/instances/instance1/opmnctl startall

But I have the error as below at  startNodeManager.sh :

Jun 17, 2014 6:01:32 PM weblogic.nodemanager.server.AbstractServerManager log
INFO: Startup configuration properties loaded from "/u01/app/bihome/user_projects/domains/bifoundation_domain/servers/bi_server1/data/nodemanager/startup.properties"

java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
        at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
        at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
        at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
        at weblogic.NodeManager.main(NodeManager.java:31)

Jun 17, 2014 6:01:33 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
        at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
        at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
        at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
        at weblogic.NodeManager.main(NodeManager.java:31)






To fix this
Add a new line to file /u01/app/bihome/wlserver_10.3/common/nodemanager/nodemanager.properties as below:

CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5

Read more:

Metalink: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager(Doc ID 1307325.1)
http://docs.oracle.com/cd/E13222_01/wls/docs100/nodemgr/java_nodemgr.html


 

Unable to add disk using oracleasm and getting Instantiating disk: failed

Unable to create the disk on RHEL6 using oracleasm

[root@racdr1 ~]# oracleasm createdisk ASM1 /dev/sdb1
Writing disk header: done
Instantiating disk: failed
Clearing disk header: done
[root@racdr1 ~]#

The reason behind this is under /etc/selinux/config file

make sure that it have following value

SELINUX=permissive

If not then set it and restart the system then issue the command again and there will be success.

[root@racdr1 ~]# cat  /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=permissive
# SELINUXTYPE= can take one of these two values:
#     targeted - Targeted processes are protected,
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

[root@racdr1 ~]# oracleasm createdisk ASM1 /dev/sdb1
Writing disk header: done
Instantiating disk: done
[root@racdr1 ~]# 

http://harvarinder.blogspot.com/2013/08/unable-to-add-disk-using-oracleasm-and.html