It actually states that you can install it in your SOA QuickStart installment as well, but I didn't try that (yet).
However, you need to extend your domain with the following items:
- Insight SOA Agent 12.2.1 [soa]
- Insight Service Bus Agent 12.2.1 [osb]
- Insight 12.2.1 [soa]
Set your FMW environment, as I put in my fmw12c_env.sh script:
[oracle@darlin-vce-db bin]$ cat ~/bin/fmw12c_env.sh #!/bin/bash echo set Fusion MiddleWare 12cR2 environment export JAVA_HOME=/usr/java/jdk1.8.0_74 export FMW_HOME=/u01/app/oracle/FMW12210 export WL_HOME=${FMW_HOME}/wlserver export NODEMGR_HOME=/u01/app/work/domains/soabpm12c_dev/nodemanager export SOA_HOME=$FMW_HOME/soa export OSB_HOME=$FMW_HOME/osb export MFT_HOME=$FMW_HOME/mft # echo call setWLSEnv.sh . $FMW_HOME/wlserver/server/bin/setWLSEnv.sh export PATH=$FMW_HOME/oracle_common/common/bin:$WL_HOME/common/bin/:$WL_HOME/server/bin:$PATH[oracle@darlin-vce-db bin]$... and navigate to the $FMW_HOME/oracle_common/common/bin folder and start config.sh:
[oracle@darlin-vce-db ~]$ . fmw12c_env.sh set Fusion MiddleWare 12cR2 environment call setWLSEnv.sh CLASSPATH=/usr/java/jdk1.8.0_74/lib/tools.jar:/u01/app/oracle/FMW12210/wlserver/modules/features/wlst.wls.classpath.jar: PATH=/u01/app/oracle/FMW12210/wlserver/server/bin:/u01/app/oracle/FMW12210/wlserver/../oracle_common/modules/org.apache.ant_1.9.2/bin:/usr/java/jdk1.8.0_74/jre/bin:/usr/java/jdk1.8.0_74/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/oracle/.local/bin:/home/oracle/bin:/u01/app/oracle/FMW12210/wlserver/../oracle_common/modules/org.apache.maven_3.2.5/bin Your environment has been set. [oracle@darlin-vce-db ~]$ cd $FMW_HOME/oracle_common/common/bin [oracle@darlin-vce-db bin]$ ls clonedunpack.sh config_builder.sh pack.sh reconfig.sh commBaseEnv.sh config.sh prepareCustomProvider.sh setHomeDirs.sh commEnv.sh configWallet.sh printJarVersions.sh unpack.sh commExtEnv.sh getproperty.sh qs_config.sh wlst.sh [oracle@darlin-vce-db bin]$ ./config.sh
In the first screen set the radio button to 'Update an existing domain':
Then Click Next, and check the items listed above:
Click Next, Next, ... Finish.
If you would have checked the 'Deployments' checkbox under the Advanced Configuration, you could have reviewed that the particular deployments are automatically targeted to the BAM, OSB and SOA clusters.
After this you can start your servers and start using insight, for example beginning with the Set up of the Insight Demo Users. This is properly described in the Quickstart Guide. But, as I'm on to it, let me try right a way. The demo users setup is downloadable here. Download it and unzip it in a folder on your server.
First we'll have to set the environment. So I call my neat fmw12_env.sh script first (in a new terminal), and explicitly set the $MW_HOME variable:
[oracle@darlin-vce-db bin]$ . fmw12c_env.sh set Fusion MiddleWare 12cR2 environment call setWLSEnv.sh CLASSPATH=/usr/java/jdk1.8.0_74/lib/tools.jar:/u01/app/oracle/FMW12210/wlserver/modules/features/wlst.wls.classpath.jar: PATH=/u01/app/oracle/FMW12210/wlserver/server/bin:/u01/app/oracle/FMW12210/wlserver/../oracle_common/modules/org.apache.ant_1.9.2/bin:/usr/java/jdk1.8.0_74/jre/bin:/usr/java/jdk1.8.0_74/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/oracle/.local/bin:/home/oracle/bin:/u01/app/oracle/FMW12210/wlserver/../oracle_common/modules/org.apache.maven_3.2.5/bin Your environment has been set. [oracle@darlin-vce-db bin]$ export MW_HOME=$FMW_HOME [oracle@darlin-vce-db bin]$ echo $MW_HOME /u01/app/oracle/FMW12210 [oracle@darlin-vce-db bin]$ echo $JAVA_HOME /usr/java/jdk1.8.0_74 [oracle@darlin-vce-db bin]$ echo $ANT_HOME /u01/app/oracle/FMW12210/wlserver/../oracle_common/modules/org.apache.ant_1.9.2
We're going to call an ant script that apparently needs the following variables set:
- MW_HOME= <Middleware home of the environment>
- JAVA_HOME= <Location of java home>
- ANT_HOME=$MW_HOME/oracle_common/modules/org.apache.ant_1.9.2
- PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH
Running the script with a developer topology domain (everything in the AdminServer or DefaultServer in the SOA QuickStart) will probably go ok. But a stuborn guy as I am tries to do this in a more production like topology with seperate SOA, OSB and BAM clusters. So it turns out that you need to adapt the insight.properties that is in the bin folder of the InsightDemoUserCreation.zip (also when you're not like me, you'll need to review it...).
After editing, mine looks like:
#Insight FOD Automation file wls.host = darlin-vce-db wls.port = 7001 soa_server_port = 7005 bam_server_port = 7006 userName = weblogic passWord = welcome1 oracle_jdbc_url = jdbc:oracle:thin:@darlin-vce-db:1521:ORCL db_soa_user = DEV_SOAINFRA oracle_db_password = DEV_SOAINFRA db_mds_user = DEV_MDS mds.password = DEV_MDS jdbc_driver = oracle.jdbc.OracleDriver
When all is right then you can run:
[oracle@darlin-vce-db bin]$ cd /media/sf_Stage/InsightDemoUserCreation/bin/ [oracle@darlin-vce-db bin]$ ant createInsightDemoUsers
Unfortunately I can't show you correct output since, although I seem to have set my properties correctly, I get failures. It turns out that my server (all in one VM) ran so slow, that Insight could not be started due to time outs in getting a database connection....
After restarting BAM all went well, except for the exceptions indicating that the users were already created.
No comments:
Post a Comment