For OEM Managed File Transfer HTTP/HTTPS hosts, the URI that creates HTTP requests is constructed at runtime with the data in the HTTP Host configuration. The OEM Managed File Transfer host configuration includes an HTTP tab that specifies the command for the mailbox, the HTTP method, the URI request path, query parameters, and headers for the request.

The migration tool does not migrate query parameters and headers. Since the migration process uses template projects, the receive project uses the HTTP GET method explicitly and the send project uses the HTTP POST method explicitly. Migration is based on the assumption that the OEM Managed File Transfer mailbox is configured with the HTTP Get method to receive files and POST method to send files. If the mailbox is configured to use other methods instead, either those mailboxes must be migrated manually or if the tool is used for migration, the generated migrated endpoints and project used in each endpoint must be edited and updated.

The migration process checks the mailbox command and the request path that is specified in the OEM Managed File Transfer host configuration. For a receive endpoint, the tool constructs a final URI with the request path and concatenates any additional path specified in the command. For the send endpoint, the final URI is same as the request path specified in the host configuration for the corresponding mailbox command.

If there is more than one command in the mailbox, only the first is considered for URI extraction. Once the URIs are extracted, they are applied to the corresponding project variable values for the relevant endpoint.