If you are moving from a traditional deployment of ASAP to a cloud native deployment, this section describes the differences between ASAP cloud native and ASAP traditional.

• ASAP Installer

  Distributed installations are not supported in the ASAP cloud native environment. All ASAP components, including WebLogic Server, must be installed in the same container.

  Also, SRT, custom SRPs, and custom NEPs are not supported in the ASAP cloud native environment.

• WebLogic Domain Configuration

  In a traditional deployment of ASAP, the WebLogic domain configuration is done using WLST or the WebLogic Admin Console. In ASAP cloud native, domain configuration is done by using WLST. ASAP cloud native does not support the deployment of ASAP in a Managed Server.

• Incoming JMS and SAF

  For incoming JMS and SAF messages, the originator must use T3 over HTTPS tunneling.

• ASAP OCA

  The Order Control Application (OCA) is available in both ASAP traditional and ASAP cloud native deployments. In a cloud native environment, you can access OCA using the hostname configured in the ASAP values.yaml file and the port number in the Traefik values.yaml file. For example, to access the OCA, use:

  https://adminhostssl.asap.org:30443/<ENV_ID>/OCA

• Web Services API

  The Web Services API is supported in the ASAP cloud native environment. The external transport protocols are HTTP, HTTPS, and JMS and the data service formats are SOAP v1.1 and 1.2.

  For details about the ASAP Web Services API supported, see ASAP Developer's Guide.