This BLOG focuses on "hands on approach" around Oracle Fusion Middleware, Oracle Service Bus, Oracle AIA, Oracle SOA Suite, Oracle Identity Management including OID, OAM, OIM, OSSO, OES, OIA, IGF, OKTA, SOA Governance using OER(Oracle Enterprise Repository), OSR(Oracle Service Registry), Oracle Big Data, WLST Scripts and Oracle Edifecs B2B Engine for HIPAA/HL7/X12/EDIFACT EDI., Amazon Elastic EC2
Shared Java EE libraries are registered with one or more WebLogic Server instances by deploying them to the target servers and indicating that the deployments are to be shared. Shared Java EE libraries must be targeted to the same WebLogic Server instances you want to deploy applications that reference the libraries.
When a referencing application is deployed, WebLogic Server merges the shared library files with the application. If you try to deploy a referencing application to a server instance that has not registered a required library, deployment of the referencing application fails with following exception
for SHA-256 with JSSE is supported in WLS 10.3.3 and higher, in conjunction
with using the JSSE SSL implementation. It is not supported when using the
Certicom SSL implementation, which is deprecated in WLS 10.3.4 and higher.
following sections describes the steps to create the self signed SHA-256
Set the WLS domain, by executing the
command setDomainEnv.sh or setDomainEnv.sh (Windows)
What is your first and last name?
What is the name of your organizational unit?
What is the name of your organization?
What is the name of your City or Locality?
[Unknown]: El Dorado Hills
What is the name of your State or Province?
What is the two-letter country code for this unit?
Is CN= soad.mindtelligent.com, OU= mindtelligent-soa, O= MindTelligent, L= El
Dorado Hills, ST= El Dorado Hills, C=US correct?
Export the certificate
-export -alias Mindteligent-SelfSigned -sigalg SHA256withRSA -file
root.cer -keystore identity.jks
Enter keystore password:
Certificate stored in file <root.cer>
Import the root certificate to the trust store:
-import -alias Mindteligent-SelfSigned -sigalg SHA256withRSA -trustcacerts
-file root.cer -keystore trust.jks
Enter keystore password:
Re-enter new password:
Please include the following parameter for startup options.
The setCompositeInstanceTitle operation is no longer supported in 12c. It has been replaced with oraext:setFlowInstanceTitle operation. To use this operation in SOA 12c (12.1.3) specifically , we need to install Patch 18310693.
Pre-install Instructions for the patch
Set the ORACLE_HOME environment variable to the directory where you have installed Oracle SOA Suite.
Stop all servers (AdminServer and all Managed server(s)).
Unzip the patch zip file into the PATCH_TOP.
$ unzip -d PATCH_TOP p18310693_121301_Generic.zip
Set your current directory to the directory where the patch is located.
$ cd PATCH_TOP/18310693
Run OPatch to apply the patch.
$ opatch apply
Once the patch has checked all the imperative prerequisites, it will prompt to proceed with installation. Please enter Y and press Enter.
On successful installation, you should see the following results.
SOA 12c 12.1.3 is now ready testing the setSlowInstanceTitle.
Changes to the Mediator
Click on the Assign button of the Mediator and setthe following property
Please ensure that you use the operation setFlowInstanceTitle() as shown below
Starting in 12c (12.1.3), we can no longer download SOA extensions. We need to use a Quick Start distribution to obtain a version of JDeveloper pre-configured for either SOA Suite or Business Process Management Suite. This thread discusses the installation of Oracle SOA Suite Quick Start.
Navigate to URL to download the zip files for SOA Suite Quick Start. Download both the files.
In a recent IoT project, MindTelligent team ran into an issue with connecting the JPA (Session Facade Client) with Session Beans when deployed on Weblogic 10.3.6 JDK 1.7 and client running on JDeveloper 184.108.40.206.
Following exception is thrown
java.io.InvalidClassException: org.eclipse.persistence.exceptions.ValidationException; local class incompatible: stream classdesc serialVersionUID = 8323218586942907354, local class serialVersionUID = 7573113798854854020
java.io.InvalidClassException: org.eclipse.persistence.exceptions.ValidationException; local class incompatible: stream classdesc serialVersionUID = 8323218586942907354, local class serialVersionUID = 7573113798854854020 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:562) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1582) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1582) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:36) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1791) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1750) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
The version of the Classorg.eclipse.persistence.exceptions.ValidationException is different in JDeveloper and Weblogic instance on which the EJB 3.0 are running.
FTP the org.eclipse.persistence_220.127.116.11_2-3.jar from the Weblogic Instance where the deployed beans are running and include it in the CLASSPATH of the client as shown below. This should resolve the issue
Shared Java EE libraries are registered with one or more WebLogic Server instances by deploying them to the target servers and indicating that the deployments are to be shared. Shared Java EE libraries must be targeted to the same WebLogic Server instances you want to deploy applications that reference the libraries. If you wish to use Jersey JAX-RS RI Version 18.104.22.168, the following shows an example of how to deploy the shared libraries that provide support for the basic Jersey JAX-RS RI functionality and JAX-RS API.
Change to the WLS_HOME/server/bin and run the command
Change to the WLS_HOME/server/lib directory
The Settings menu allows you to customize the look and feel of your organization. Admins can customize elements such as headings, labels, and the appearance of the Okta My Applications or "home" page, as well as the look and feel of the activation email. The Settings menu also includes a Downloads option to the latest browser plug-ins and admin downloads.
The Settings menu is an option on the Administrator Dashboard:
As an admin, you can supply contact information for your org, including organization, end-user support, billing, and technical contacts. You can also give Okta Support temporary access to your account for troubleshooting purposes, and can select the type of email notifications you want to receive. The Account page hosts all of this information.
Select Settings > Account.
Click the corresponding Edit link to specify the following:
Organization Contact: Used by Okta to communicate with your organization.
End User Support Contact: Enter a support phone number that will display on Okta help pages.
Technical Contact: Receives notices when users send a help request. The email address appears on all new user registration emails.
Billing Information: Used by Okta for billing purposes.
Give Access to Okta Support: By default this is Disabled. If you want to allow Okta Support to login to your account as an administrator for troubleshooting purposes, click Edit, then change this option toEnabled. Access is only enabled for 8 hours; after which you will need to re-enable access for Okta Support again.
Email Notifications: Configure which email notifications are sent to you by doing the following:
From your Administrator Dashboard, select Settings > Account, and then click Edit in the Email Notifications section.
For each email notification that you want to receive, select the corresponding check box.
Once you have made any changes to your account settings, click Save.