FDMEE to Cloud Integration in 11.2.x
The instructions for FDMEE On-Prem to Cloud (PBCS, FCCS) in the 11.2.x readme are based on the method for 11.1.2.4 as it contains references to the v10 release of Weblogic and a specific jdk version. While this could be pretty simple for the tech savvy to interpret to WebLogic 12c etc. this might save you some time.
First get the certificate from the target PBCS/FCCS Pod. In Firefox for example:
Click the padlock -> Connection Secure -> More information
Click PEM (cert) and save under D:\Oracle\PBCSCert as pbcs.crt
Run the command prompt as 'Administrator':
cd D:\Oracle\Middleware\wlserver\server\lib
D:\Oracle\Middleware\jdk\jre\bin\keytool -importcert -keystore DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase -file D:\Oracle\PBCSCert\pbcs.crt -alias "planning-xxxxxx.pbcs.em3"
Where xxxxxx is the target pod id domain:
Note, this is the entry from the 11.2.8 FDMEE Read me (section 3-62) which is based on 11.1.2.4. The items in red are where it differs in 11.2 as the installer does not label the Weblogic or jdk versions (11.2.8)
At a command prompt, type: cd
C:\Oracle\Middleware\wlserver_10.3\server\lib.
b. Type: C:\Oracle\Middleware\jdk1.8.0_181\jre\bin\keytool -importcert -
keystore DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase -file
c:/temp/pbcs.crt -alias "pbcs_pod_name"
Using the WebLogic Admin Console, modify two WLS SSL settings.
a. Login to the WebLogic Admin Console.
b. Select Lock and Edit.
c. Select Servers, and then ErpIntegrator0.
d. Select SSL and then expand Advanced. - Ignore, see below
e. Enable JSEE SSL. – not in WebLogic 12c as it uses JSEE by default and there is no option to select it
f. In Hostname Verification, select Customer Hostname Verifier.
g. In Custom Hostname Verifier, enter:
weblogic.security.utils.SSLWLSWildcardHostnameVerifier.
h. Save and activate changes.
FDMEE Target application
creation (Cloud) - enter the pod details:
Save
Hit 'Refresh Members' and you should be good to go!