Run OAS 5.5.0 automatically after linux system reboot

mchorazy

Hi everyone,

Can anybody tell me how can I configure OAS 5.5.0 to run automatically after system linux reboot?

I have command start.sh in: /u01/app/oracle_oas/user_projects/domains/oasbiee/bitools/bin/start.sh

I can run it manually with this command /u01/app/oracle_oas/user_projects/domains/oasbiee/bitools/bin/start.sh or su oracle -c "/u01/app/oracle_oas/user_projects/domains/oasbiee/bitools/bin/start.sh"

But how can I configure this script in Oracle Linux 6.9 (Red Hat) to run this script after reboot?

Gianni Ceresa

That's something your OS has to deal with.

For example https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/installation_guide/s1-boot-init-shutdown-r…  or a custom script executing the command you would run by hand (making sure it will be executed as the correct user) in init.d.

You can also write a whole service with dependent services etc., but that's up to you.

mchorazy

I try with rc.local add something like that: su oracle -c "/u01/app/oracle_oas/user_projects/domains/oasbiee/bitools/bin/start.sh"

Jednak wtedy dostaję błąd:

<Jul 23, 2020 10:45:33 AM CEST> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.><Jul 23, 2020 10:45:33 AM CEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.><Jul 23, 2020 10:45:33 AM CEST> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>Node manager not running. Starting it...NMProcess: NODEMGR_HOME is already set to /u01/app/oracle_oas/user_projects/domains/oasbiee/nodemanagerNMProcess: + /usr/java/jdk1.8.0_261-amd64/bin/java -server -Xms32m -Xmx200m -Djdk.tls.ephemeralDHKeySize=2048 -Dcoherence.home=/u01/app/oracle_oas/wlserver/../coherence -Dbea.home=/u01/app/oracle_oas/wlserver/.. -DNodeManagerHome=/u01/app/oracle_oas/user_projects/domains/oasbiee/nodemanager -DLogToStderr=false -DQuitEnabled=true -Dweblogic.RootDirectory=/u01/app/oracle_oas/user_projects/domains/oasbiee -Doracle.security.jps.config=/u01/app/oracle_oas/user_projects/domains/oasbiee/config/fmwconfig/jps-config-jse.xml -Dcommon.components.home=/u01/app/oracle_oas/oracle_common -Dopss.version=12.2.1.3 -Dweblogic.RootDirectory=/u01/app/oracle_oas/user_projects/domains/oasbiee -Doracle.bi.home.dir=/u01/app/oracle_oas/bi -Doracle.bi.config.dir=/u01/app/oracle_oas/user_projects/domains/oasbiee/config/fmwconfig/biconfig -Doracle.bi.environment.dir=/u01/app/oracle_oas/user_projects/domains/oasbiee/config/fmwconfig/bienv -Doracle.bi.12c=true -Ddomain.home=/u01/app/oracle_oas/user_projects/domains/oasbiee -Dfile.encoding=utf-8 -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -Djava.security.policy=/u01/app/oracle_oas/wlserver/server/lib/weblogic.policy -Dweblogic.nodemanager.JavaHome=/usr/java/jdk1.8.0_261-amd64 weblogic.NodeManager -vNMProcess: CLASSPATH=/usr/java/jdk1.8.0_261-amd64/lib/tools.jar:/u01/app/oracle_oas/wlserver/server/lib/weblogic.jar:/u01/app/oracle_oas/wlserver/../oracle_common/modules/thirdparty/ant-contrib-1.0b3.jar:/u01/app/oracle_oas/wlserver/modules/features/oracle.wls.common.nodemanager.jar::/usr/java/jdk1.8.0_261-amd64/lib/tools.jar:/u01/app/oracle_oas/wlserver/modules/features/wlst.wls.classpath.jar:/u01/app/oracle_oas/wlserver/..:/u01/app/oracle_oas/wlserver/modules/features/oracle.wls.common.grizzly.jarNMProcess: Jul 23, 2020 10:45:37 AM oracle.security.jps.internal.config.xml.XmlConfigurationFactory validateFileLocationNMProcess: INFO: JPS Config: /u01/app/oracle_oas/user_projects/domains/oasbiee/config/fmwconfig/jps-config-jse.xmlNMProcess: Jul 23, 2020 10:45:40 AM oracle.security.opss.internal.runtime.ServiceContextManagerImpl getContextNMProcess: WARNING: Bootstrap services are used by OPSS internally and clients should never need to directly read/write bootstrap credentials. If required, use Wlst or configuration management interfaces.NodeManager startedReading domain.../Servers/AdminServer/ListenPort=9500Accessing admin server using URL t3://.....Starting AdminServer ...Admin Server Start Exception: Error occurred while performing nmStart : Error Starting server AdminServer : Received error message from Node Manager Server: [Server start command for WebLogic server 'AdminServer' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'AdminServer' log for detailed information.]. Please check Node Manager log for details.Use dumpStack() to view the full stacktrace :Unable to connect to AdminServer on host: ....Fatal: Failed to start one or more Servers (return 3)

In log is authenticated error, that username/password incorrect...and only when I add this line I get this problem. When after reebot I use start.sh manually it's working.

When I get this error I must do steps like here: https://shivabizint.wordpress.com/2012/10/15/how-to-reset-the-lost-weblogic-admin-user-password/  -- reset weblogic password.

Any idea?