• If SSL is disabled in the source environment before the migration.
• If there is an external reference from a SOA composite to another SOA composite WSDL or service using a non-SSL URL, which changes.

  Workaround:

  For this case, the SOA composite must be updated to avoid the usage of hard coded URL using a token or a Load Balancer URL, which remains valid after the upgrade.

• All the call backs from external systems for the instances created before the upgrade might fail if the call back is made to the SOA instance with an old SOA server URL, which gets modified as part of the upgrade.

  Workaround:

  For this case, you can temporarily enable the non-SSL URL to recover call back of instances. However, this might not work for all the cases. Ensure that there are no open instances expecting call backs from external systems before the upgrade.

• If SSL is enabled in the source environment before the migration, and the protocol, host, and port remain unchanged as part of the upgrade.
• If the customer is using Oracle HTTP Server or Load Balancer URL as the SOA Server URL, which is used to route calls and if all the external interactions occur through the SOA Server URL (assuming that the URL remains unchanged).

• errorPage.jspx error is thrown when you access Enterprise Manager Fusion Middleware Control (https://hostname:port/em).
• Failure of Web Server bridge: No backend server available for connection error is thrown when you access soa-infra node (https://hostname:port/soa-infra).

1. Navigate to Edit Tree, under Environment select Servers.
2. Click New.
3. Specify a name for the managed server.
4. From Copy settings from another server drop-down, select an existing managed server.
5. Click Create.
6. In Edit Tree, navigate to the newly created server. For example, WLS_SOA5.
7. In the General tab, update and specify a unique number in the Local Administration Port Override field. Ensure that all the managed servers in the domain on the same machine have unique administration port values (>=1024).
8. Click Save.

   A message confirms that the changes are added to the shopping cart.

9. Navigate to the Security tab, and then select Keystores.
10. In the Keystores tab, specify the Custom Identity Key Store Pass Phrase and Custom Trust Key Store Pass Phrase.
11. Click Save.

    A message confirms that the changes are added to the shopping cart.

12. Navigate to the SSL tab and specify the Server Private Key Pass Phrase.
13. Click Save.

    A message confirms that the changes are added to the shopping cart.

14. Navigate to the Shopping Cart in the top-right corner of the WebLogic Remote Console window and click Commit Changes.
15. Start the managed server.

    Sample Command:

    cd /u02/oracle/config/domains/base_domain_1/bin
            ./startManagedWebLogic.sh WLS_SOA5
            https://soaexternal.oraclevcn.com:9002
            -Djavax.net.ssl.trustStore=/u01/oracle/config/keystores/soahost1/trust.p12
             
          -Djavax.net.ssl.trustStorePassword=WElcome1_1_

1. Log in to Enterprise Manager Fusion Middleware Control.
2. Navigate to SOA Infrastructure and select SOA Folder.
3. Select Default and then navigate to the Deployed Composite tab.

   The following error message is displayed in the browser: Retrieval failed with error java.lang.reflect.UndeclaredThrowableException. Please view the log file for details.

JAVA.LANG.ILLEGALSTATEEXCEPTION: CANNOT CONVERT VALUE OF TYPE 'JDK.PROXY7.$PROXY447

[test_log] [INFO] [exec] Connecting to
        t3s://phxpffag40.dev2farmphx3.screvenfar02phx.oraclevcn.com:9002 with userid
        partitioncomposeruser ...
      [test_log] [INFO] [exec] <Jul 10, 2024, 6:14:55 AM Pacific Daylight Time> <Info>
          <Security> <BEA-090908> <Using the default WebLogic SSL Wildcard Hostname Verifier
          implementation.> 
      [test_log] [ERROR] [exec] This Exception occurred at Wed Jul 10 06:14:55 PDT
        2024.
      [test_log] [ERROR] [exec] java.lang.SecurityException: User partitioncomposeruser does
          not have access to the administrator port.

• Admin role : Read & Write Access
• Monitor role : Read Access
• App Tester role : Read Access

1. Remove the application server connection created using the localhost.
2. Remove the system file generated by the JDeveloper while starting the JDeveloper. For example : /home/<userid>/.jdeveloper.
3. Open the JDeveloper and create the application server connection using the hostname as, for example, myhost.com.
4. Now, deploy the SOA sample using the application server connection.