Managing SOA CS domains with Myst
Last updated
Last updated
A SOA Cloud Service (SOA CS) environment can be introspected to create a Platform Blueprint and Platform Model.
The article will guide users through the introspection process specifically for SOA CS environments.
Create a Cloud Infrastructure for MyST to access the SOA CS environment.
Hover over Discover and click Cloud Services
Click Discover > Cloud Infrastructure
Enter a Name such as Default
Click
Enter the Name and Private Key Content and click
Click
Enter the Name, SSH User Name, Key Pair
Select Yes for Run as different user and enter oracle as the Other User Name
Click
Retrieve the Public IP from your Oracle Cloud account
Enter Name, Host Name and select Compute Logical Definition, Environment, OS Agent Credential
Click to validate the SSH connection is successful then click
Click
The discovery process reads the SOA CS environment into MyST.
Click Discover > Soa Cloud Service
Select the SOA 12.2.1.2 Blueprint
Below are the Blueprint configuration changes to align MyST with SOA CS
WebLogic Domain Configuration > Coherence Clusters > defaultCoherenceCluster
Cluster Listen Port
9991
7574
SOACS uses 7574 while SOA on-premise was 9991
WebLogic Domain Configuration > WebLogic Deployment Targeting > Applications > wsm-pm
Targets
AdminServer, soa_cluster
AdminServer
(Optional) Remove the soa_cluster so only the AdminServer is targeted
WebLogic Domain Configuration > JDBC Data Sources > All OOTB
Test Table Name
SQL SELECT 1 FROM DUAL
SQL ISVALID
(Optional) Set the value for each out of the box (OOTB) Data Source
WebLogic Domain Configuration > JDBC DataSources
wlsbjmsrpDataSource
N/A
Name, Targets, JDNI Name, and Driver Class Name
(Optional) Only necessary if users want to change configuration for wlsbjmsrpDataSource
WebLogic Domain Configuration > JCA Adapters
Outbound Connection Properties
N/A
Any properties
MyST currently does not introspect Outbound Connection Properties. Add if you have any JCA Adapters configured.
WebLogic Domain Configuration > Clusters
Cluster Address
Auto computed by MyST
Auto computed by MyST (cannot be removed)
(Optional) MyST computation requires the Cluster Address to always be set
WebLogic Domain Configuration > AdminServer > Default Store
Directory
${[rxr.wls.Domain-1].shareHome}/tlogs
${[rxr.wls.Domain-1].domainAserverHome}/servers/${[rxr.wls.AdminServer-1].name}/data/store/default
By default TLOGS are not defined in the WLS Console. In MyST we set them to their default directory.
WebLogic Domain Configuration > Managed Servers > Default Store
Directory
${[rxr.wls.Domain-1].shareHome}/tlogs
${[rxr.wls.Domain-1].domainAserverHome}/servers/${[rxr.wls.ManagedServer-1].name}/data/store/default
By default TLOGS are not defined in the WLS Console. In MyST we set them to their default directory.
MyST has a check for drift function to compare the current MyST Platform Instance against the SOACS environment.
Below are safe and optional properties/values which can be used as MyST defaults in the Blueprint. They are the optional properties taken from the table above in the Blueprint section.
WebLogic Domain Configuration > WebLogic Deployment Targeting > Applications > wsm-pm
Targets
AdminServer, soa_cluster
AdminServer
WebLogic Domain Configuration > JDBC Data Sources > All OOTB
Test Table Name
SQL SELECT 1 FROM DUAL
SQL ISVALID
WebLogic Domain Configuration > JDBC DataSources
wlsbjmsrpDataSource
N/A
Name, Targets, JDNI Name, and Driver Class Name
WebLogic Domain Configuration > Clusters
Cluster Address
Auto computed by MyST
Auto computed by MyST (cannot be removed)
Question: Does MyST support an administrative user other than the weblogic username?
Answer: No, at this point a weblogic username is required. Admins can create an additional weblogic user.
Hover over Discover and click Cloud Services
Enter a Name and click
Enter the Domain home directory, Platform Model, and Password and click Discover
After the discovery finishes loading click
Review your instance definition and click
Click Manage > Platform Blueprints
After the discovery and configuration of a Blueprint it is good practice to validate the changes against the SOA CS environment. A dry run functionality mimics the configuration applied by MyST and outputs the changes. Below is an example of changes to the Cluster Address and a JDBC Datasource.
