Rogerio Antonio

In this post, I am writing to create a boot properties in  Linux/Unix and Windows. Just a recap and for the readers not used to play with Oracle Fusion Middleware / WebLogic, the general steps to build an Oracle Fusion Middleware available are. Chose the version – and check the certification matrix again your business requirements Download the software : Oracle Fusion Middleware  + Java Install the software Create Domain Domain creation, when the servers start the startWeblogic .* scripts in the process in an iterative mode, will ask the WebLogic credentials. The way to avoid that is to provide a file called boot.properties , the location for the file is inside the domain home/servers/<servername>/security ( this folder needs to be created ) . eg. Linux/Unix: ${DOMAIN_HOME}/servers/AdminServer/security/boot.properties Windows : %domain_home%\servers\AdminServer\security\boot.properties It means that after the 4 step – the next action will be create that boot.properties ...

Versao Portuguesa This post is about how to create database schema for Oracle Fusion Middleware, using the Repository Creation Utility (RCU). In Command line - This bellow reproach can be used for automation

English Version Este post e sobre a criacao do repositorio pra produtos Oracle Fusion Middleware, usando o utilitario Repository Creation Utility (RCU), em linha de comando - silent mode - esta abordagem pode ser usada pa automacao.

EnglishVersion Este post tem como objectivo mostrar a instalacao de Oracle Fusion Middleware Infrastructure de uma forma rapida e facil - usando o modo silent - esta abordagem pode ser usada para automacao

Versao Portuguesa The aim of this post is to show how to install the Oracle Fusion Middleware Infrastructure in a fast and easy way - this approach could be also used for the automation

PT :   FRM-91500 - Resolução EN :  FRM-91500 - Solved

Weblogic 11g $find $DOMAIN_HOME -name *.properties | xargs grep IS_CLUSTERED ./user_projects/domains/orwms_sit1/servers/WLS_FORMS/tmp/formsapp/11.1.1/install-plan.properties:IS_CLUSTERED=false ./user_projects/domains/orwms_sit2/servers/WLS_FORMS/tmp/formsapp/11.1.1/install-plan.properties:IS_CLUSTERED=false $find $DOMAIN_HOME -name *.properties | xargs grep IS_CLUSTERED ./user_projects/domains/orwms_0719/servers/WLS_FORMS1/tmp/formsapp/11.1.1/install-plan.properties:IS_CLUSTERED=true ./user_projects/domains/orwms_0718/servers/WLS_FORMS/tmp/formsapp/11.1.1/install-plan.properties:IS_CLUSTERED=true ./user_projects/domains/orwms_0720/servers/WLS_FORMS/tmp/formsapp/11.1.1/install-plan.properties:IS_CLUSTERED=true ./user_projects/domains/orwms_0739/servers/WLS_FORMS1/tmp/formsapp/11.1.1/install-plan.properties:IS_CLUSTERED=true Weblogic 12c # # Other way # grep -i cluster $DOMAIN_HOME/config/config.xml | sort -u </cluster> <cluster> <cluster-constraints-enabled>fal...

PT :   IS_CLUSTERED  EN :  IS_CLUSTERED

Weblogic 11g # # start weblogic # cd $WL_DOMAIN nohup ./startWebLogic.sh & # # start Node Manager # cd $WL_HOME/server/bin nohup ./startNodeManager.sh & Weblogic 12g # # auto login # mkdir -p $DOMAIN_HOME/servers/AdminServer/security echo "username=weblogic" > $DOMAIN_HOME/servers/AdminServer/security/boot.properties echo "password=Welcome0" >> $DOMAIN_HOME/servers/AdminServer/security/boot.properties # #start Node Manager # cd $DOMAIN_HOME/bin nohup ./startNodeManager.sh > ~/startNodeManager.nohup.out 2>&1 & # # start weblogic # cd $DOMAIN_HOME/bin nohup $DOMAIN_HOME/startWebLogic.sh > ~/startWebLogic.nohup.out 2>&1 & # # start MS # nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 http://wls-server:7001 > ~/soa_server1.nohup.out 2>&1 & nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server2 http://wls-server:7001 > ~/soa_server2.nohup.out 2>&1 & nohup $DOMAIN_HOME/bin/startManaged...

PT :   Start Weblogic EN :  Start Weblogic cd $WL_DOMAIN nohup ./startWebLogic.sh & cd $WL_HOME/server/bin nohup ./startNodeManager.sh &

Versao Portuguesa Sometimes is useful to trace the session from the beginning, for that is useful to use a logon trigger eg RPM batches I'm sharing three logon trigger examples to help in that situations, the first one using the client hostname, if you know it.  SQL> drop trigger sys.set_trace_rpm; SQL> create or replace trigger sys.set_trace_rpm after logon on database when (user in ('RPM_OAS')) declare retail_module varchar(200); begin select module into  retail_module from gv$session where sid =  upper(sys_context('userenv','sid')) and (osuser is null and machine like 'rpm_app_server%'); execute immediate 'alter session set statistics_level=all';  execute immediate 'alter session set max_dump_file_size=unlimited';  execute immediate 'alter session set events ''10046 trace name context forever, level 12''';  execute immediate 'alter session set tracefile_identifier=''RA_RPM'''; e...