Configure a Java Mail Session

Only Oracle Cloud at Customer This topic applies only to Oracle Cloud at Customer.

When using AppToCloud to create an Oracle Java Cloud Service instance, you must configure the location of any Java Mail Sessions that were present in your source Oracle WebLogic Server domain.

A Java Mail session provides applications running on WebLogic Server with access to mail servers through either the Internet Message Access Protocol (IMAP) or Simple Mail Transfer Protocol (SMTP) mail protocols. The configuration for a mail session includes the location of the mail server for sending messages and the location of the mail server for receiving messages.

  1. From the Additional Service Details page of the AppToCloud instance creation wizard, expand Java Mail Session.
  2. Select the name of the mail session.
  3. Click Disable if you want to remove this mail session from the service instance. Otherwise continue to the next step.
  4. Update the configuration for this mail session:
    Field Description

    Mail Session Name

    The name of the mail session you selected. This field is read-only.






    Enter the protocol, host name, port and credentials (if required) of the mail server:

    • For sending messages (Send)

    • For receiving messages (Receive)

    • To be used by default for both sending or receiving messages (Default)

    If a Host is not configured in either the Send or Receive sections, you must configure a Default host.

    Bypass Precheck

    By default, Oracle Java Cloud Service will validate the connection to this mail server and continue with the AppToCloud import operation only if it succeeds. Select this check box to skip the validation of this provider.


    You can also directly update the standard Java Mail properties found in the Optional Properties text area.
  5. Click OK to accept your changes. Repeat these steps for each additional mail session in the Java Mail Session list.

    A check mark icon indicates a resource that you have already configured.

  6. Continue with the creation of this service instance.