How to find SOA Suite version

Follow below steps for finding SOA version
1.Source env
soadev2@test2:~$ . /u01/soadev2/infr/user_projects/domains/isg_domain/bin/setDomainEnv.sh
*****************************************************
** Setting up SOA specific environment...
*****************************************************
EXTRA_JAVA_PROPERTIES= -da:org.apache.xmlbeans...
.
LD_LIBRARY_PATH=:/u01/soadev2/db_fmssodv2/product/12.1.0/dbhome_1/lib:/u01/soadev2/infr/wlserver/server/native/solaris/sparc64:/u01/soadev2/infr/wlserver/server/native/solaris/sparc64/oci920_8
.
.
*****************************************************
** End SOA specific environment setup
*****************************************************

2.Go to $SOA_ORACLE_HOME/bin
soadev2@test2:/u01/soadev2/infr/soa/bin$ cd $SOA_ORACLE_HOME/bin
soadev2@test2:/u01/soadev2/infr/soa/bin$ pwd
/u01/soadev2/infr/soa/bin

soadev2@test2:/u01/soadev2/infr/soa/bin$ ./soaversion.sh
**************************************************************
INFO: Detected a WebLogic Installation.
**************************************************************
Oracle SOA Suite Version Information:
-------------------------------------

Product Version : 12.2.1.2.0-161003.0739.0018
Label Version   : PCBPEL_12.2.1.2.0_GENERIC_161003.0739.0018
Compile JDK     : 1.8.0_40-ea
Java Home       : /export/home/soadev2/jdk/jdk1.8.0_74

Runtime JDK Version
java version "1.8.0_74"
Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)
**************************************************************
soadev2@hofsoadev2:/u01/soadev2/infr/soa/bin$

Comments

Post a Comment

Popular posts from this blog

Steps to run Autoconfig for patch File system 12.2

1.       To run Autoconfig from the patch file system you must disable trigger ebs_login prior to running autoconfig. SQL> show user; USER is "SYSTEM" SQL> alter trigger ebs_logon disable; Trigger altered. 2.       Now run autoconfig with the patch env sourced [appltest@test001]$ echo $FILE_EDITION [appltest@test001]$patch [appltest@test001]$ adautocfg.sh Make sure Autoconfig completes ok      3. Enable the login trigger “alter trigger ebs_logon enable”                  SQL> conn system/Oracle4u                  Connected.                SQL> SQL> alter trigger ebs_logon enable;                 Trigger altered.
Read more

ADOP fs_clone failing with ERROR: Managed Server's are not in sync between file system context and DB context

 adop fs_clone failing with below error. +++++++++++++++++++++++++ configProperty id = Server11 Count for NodeIterator nextNode = 3 ERROR: Managed Server's are not in sync between file system context and DB context ERROR: Update Moveplan Fail START: Inside exitClone.... Updating status INCOMPLETE for ApplywlsTechStack START: Updating status INCOMPLETE for action ApplywlsTechStack END: Updated status INCOMPLETE for action ApplywlsTechStack SOLUTION Please follow the solution in  Doc ID 2232990.1  and advise accordingly To resolve the issue test the following steps in a development instance and then migrate accordingly: 1. Unlock the configuration in the weblogic console via the following steps: A. Open a browser and enter the weblogic console URL eg: https ://localhost:port/console as the administrator. B. Navigate to the weblogic server administration Applications Configuration console. C. Unlock the weblogic server configuration by clicking 'Release Configuration' option.
Read more

txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials

 txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials validate_apps_password.log Pattern found... ================ EXIT STATUS: 1 Invalid APPS database user credentials. Solution Check  lsnrctl status <listener_name>,check files under $TNS_ADMIN,check environment,Check if case sensitive login is enabled and if enabled,disable it
Read more