Migration to 12c for ADF SOA application from 11.1.1.7 – part 2
In this blog you will learn how to create and configure local environments for the process of migration to 12c. You can also read Migration to 12c for ADF SOA application from 11.1.1.7 – part 1.
I. How to install Oracle BPM Studio 12c
1.Prerequisites:Need to have jdk 1.8
2.Install:
2.1. Download Oracle BPM Suite 12c version 12.2.1.2.0 from here:
2.2. Unzip all 2 archives in one directory:
For example:
C:\install\12cRC2
2.3. Open cmd like Administrator in your local Java installation directory and run:
C:\Oracle\Java\jdk1.8.0_101\bin\java.exe -jar (full path)/fmw_12.2.1.2.0_bpm_quickstart.jar
3. JDev BPM studio tuning:
(See Tune your JDeveloper 12c (12.1.3))
Step 1: Configure JVM settings in jdev.conf
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
Path: $MV_HOME$/jdeveloper/jdev/bin/jdev.conf # optimize the JVM for strings / text editing AddVMOption -XX:+UseStringCache AddVMOption -XX:+OptimizeStringConcat AddVMOption -XX:+UseCompressedStrings # if on a 64-bit system, but using less than 32 GB RAM, this reduces object pointer memory size AddVMOption -XX:+UseCompressedOops # use an aggressive garbage collector (constant small collections) AddVMOption -XX:+AggressiveOpts # for multi-core machines, use multiple threads to create objects and reduce pause times AddVMOption -XX:+UseConcMarkSweepGC AddVMOption -DVFS_ENABLE=true AddVMOption -Dsun.java2d.ddoffscreen=false AddVMOption -XX:+UseParNewGC AddVMOption -XX:+CMSIncrementalMode AddVMOption -XX:+CMSIncrementalPacing AddVMOption -XX:CMSIncrementalDutyCycleMin=0 AddVMOption -XX:CMSIncrementalDutyCycle=10 |
Step 2: Configure Jdeveloper memory settings in ide.conf
|
1 |
Path: $MV_HOME$/jdeveloper/ide/bin/ide.conf # Set the default memory options for the Java VM which apply to both 32 and 64-bit VM's. # These values can be overridden in the user .conf file, see the comment at the top of this file. AddVMOption -Xms2048M AddVMOption -Xmx4096M |
Step 3: Disable “Build After Save”
Follow this link
Step 4: Integrate jad decompiler in JDeveloper
Add at the end of jdev.conf file:
|
1 |
AddVMOption -Djcncmd=C:\install\jad\jad.exe -& -p -b -ff -nl -pi99999 -space -t2 -noinner |
II. Create and configure Integrated WebLogic
1.Start JDeveloper 12c and create integrated weblogic server:
Following wizard set
1. Name
2. Username and password for admin account
3. WebLogic
Host : localhost
Port : 7101 (SSL port is not used but need to set)
Domain name
2. Configure Integrated WebLogic:
2.1. Setup Default Server
Run Integrated WL from JDeveloper
Open http://localhost:7101/console
Navigate to Environment –> Severs
–> Choose Default Server:
Set “Listen Address:” to localhost
Uncheck “SSL Listen Port Enabled”
2.2. Add needed credentials in cred store (get them from previous 11g environment)
2.3. Configure PolicyStore
2.4. Create data sources
2.5. Create alsb-system-user in WL console in Administrators Role
“alsb-system-user” is created automatically when you set up WL server. Go to WLS console -> Security Realms -> myrealm -> Users and Groups tab -> Users tab
and check if it is created. If you see alsb-system-user in the table you are ready with this step.
2.6. Setup DbAdapter
Navigate to Deployments -> DbAdapter
Click on DbAdapter and go to:
–> Configuration –> Outbound connection pools:
for –> javax.resource.cci.ConnectionFactory – click +
And set up your DbAdapter (like in 11g environment)
2.7. Setup “Protected Flex Fields” in BPM (like in 11g environment)
2.8. Setup LDAP (if need)
In case of need to use ‘virtualize’ in order to use DefaultAutentication provider and external authentication providers you have to apply the following patch
Stop IntegratedWL.
in the $DOMAIN_HOME/config/fmwconfig/jps-config.xml to make it look like this (the new lines are displayed in bold font):
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
<serviceInstance name="ad" provider="idstore.ldap.provider"> <!-- Add any properties that we want to override --> <property value="sAMAccountName" name="username.attr"/> <property value="sAMAccountName" name="user.login.attr"/> </serviceInstance> <serviceInstance name="idstore.ldap"provider="idstore.ldap.provider"> <description>LDAP Identity Store Service Instance</description> <property name="virtualize" value="true"/> <property name="idstore.config.provider" value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider"/ <property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/> <serviceInstanceRef ref="ad"/> </serviceInstance> |
where “ad” is the name of the AD identity provider you created in WLS console. In other words, the name of the service instance must match the name specified in the $DOMAIN_HOME/config/config.xml file:
|
1 2 3 4 |
<sec:authentication-provider xsi:type="wls:active-directory-authenticatorType"> <sec:name>ad</sec:name> <sec:control-flag>SUFFICIENT</sec:control-flag> ..... |
Then, in the $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml file in the section for LDAP provider (easy to be found by provider name), add the cn to sAMAccountName mapping like so:
|
1 2 3 4 5 6 7 8 9 10 |
<plugin> <name>UserManagement</name> <class>oracle.ods.virtualization.engine.chain.plugins.usermanagement.UserManagement</class> <initParams> <param name="directoryType" value="activedirectory"/> <param name="mapAttribute" value="orclGUID=objectGuid"/> <param name="mapAttribute" value="cn=sAMAccountName"/> <param name="mapAttribute" value="uniquemember=member"/> </initParams> </plugin> |
Finally Start IntegratedWL.
I’m curious to learn about your experience on the topic, so do not hesitate to share your opinion in the comments section below.
