Partner Onboarding with Partner-Initiated Connection

This activity is used for onboarding partners in situations where the partner connects to the sponsor to send and receive files.

  1. Enter sponsor information:
    1. Provide partner contact details by clicking Start Task in the Status/Action column. The Partner Information window opens, showing pre-populated contact details.
    2. Edit contact details, if necessary, and click Next.
      Note: In case the Client Authentication parameter is not provided, then you will be prompted to provide this information after clicking the next button.
    3. You can provide the same Partner ID with Partner Names being unique.
    4. Select the check box "Envelope Creation is not required", if envelope is not required for the partner and Click Next.
  2. Provide partner connectivity information –
    1. Click Start Task in the Status/Action column to launch the Protocol and Direction Info wizard.
    2. Select the preferred protocol from the Protocol drop down.
    3. Select the type of direction – Inbound, Outbound, or Both – from the Direction menu.
    4. Select the type of transfer – MFTB2B, or Both – from the Transfer Type drop down.
      1. For B2B transfers, set the EDI standard to either X12 or EDIFACT. Further transaction options are based on this selection.
    5. Under Environment, set the environment type to either Production or Non-production, or Both, as required.
    6. Select Push from the Outbound to customer drop down.
    7. Select Pull from the Inbound to customer drop down.
  3. Configure partner's network IP address and connection details –
    1. Provide the IP addresses of the production and non-production servers to be whitelisted.
    2. Upload the certificates for client authentication for production and non-production instances.
      Note: You will be prompted to upload the certificate in case the client authentication is set to true.
    3. In Preferred Authentication Type, select PASSWORD and SSH Key.
    4. Upload the SSH Authorized User Key.
    5. Provide a name for the uploaded Authorized User Key.
    6. Provide the PGP key, by using the Upload PGP Key Upload button. Also, download the PGP Key of the Sponsor.
    7. Click Next.
    8. Enter the authorized key in the SSH Keys field.
    9. Click Next.
  4. Perform service selection and configure the envelope template process –
    1. Click Start Task in the Status/Action column to open the KeyGrabber, PGP, IP Whitelist window.
    2. Select the System Certificate Store and Trusted Certificate Store from the respective drop down menus.
      Note: The System Certificate Store and Trusted Certificate Store input is prompted if it is not in the context data and the Enable parameter is set true under SSP section.
    3. Select the Policy Name, Security Settings, and System Certificate from the respective drop down menus and then select the supported Ciphers check boxes.
      Note: The above parameters are prompted if it is not set in the context data and the Enable parameter is set true under SSP section.
    4. Select the supported Ciphers for confirmation.
      Note: You will be prompted to confirm the supported Cipher, which has been set in the context data and Enable parameter is set true under SSP section.
    5. Select the Adapter Name or Adapter Service Group Name from the Select the Adapter Name drop down menu.
    6. Select the polling interval from the Application drop down.
    7. Select the correct application from the drop down.
    8. Click Next.
    9. You will be prompted with a screen showing the PGP Key ID. Click Next.
    10. Select the IP Whitelist check box.
      Note: You will be prompted to confirm the IP whitelisting if:
      • Enable parameter is set to not true under SSP section. This is to ensure the partners’ IP is whitelisted.
      • Enable parameter is set to true under SSP section. This is to ensure the partners’ IP is whitelisted at your RMZ Firewall and to ensure the partner connection is established to your local balance/SSP.
    11. Click Yes to finish.
  5. Perform a user account setup test by entering partner details in the test environment.
    1. Enter the partner's user ID to login to the server.
    2. Specify the virtual root path, which is the first level of directory path to the mailbox.
    3. Specify the path to which file is to be dropped by the partner i in the Directory field.
    4. Specify the path from which file is to be picked up by the partner in the Out Directory text field.
  6. Set up the data flow between the partner and application in the non-production environment –
    1. Click Start Task in the Status/Actions column to open the Set Up Data Flow window.
    2. The Select Data Flow template is displayed. It is pre-populated with values that were configured earlier.
      Note: To know more about where it configured, see Data Flow Template Configuration.
    3. Click Next.
    4. Select the direction of the file – Inbound, Outbound, or Both.
    5. Click Next.
    6. In Doc Type, select the appropriate document type.
    7. Enter the file name pattern of the file which will be sent in the File Name field.
    8. Enter the file name pattern of the file, if MFT is document type is selected and Enter the Transaction, Sender ID, Receiver ID if X12 or EDIFACT document type is selected.
    9. In Select Rules, select the required rules and change values if needed.
    10. Click Next.
    11. Wait for the Provisioning Hub system test to complete. This test is used to validate the auto approval process. Click the Refresh button until the process is approved or fails.
  7. An email with connection details and login credentials is sent to the partner. The partner should use this information to verify the connection.
  8. Wait for the following system tasks to complete:
    • Connectivity Test.
    • Wait for Testing.
    1. An automated process checks the connection details. The process returns an approval status if connection details are correct; otherwise, the task fails. Click the Refresh button until this process is approved or fails.
      • If any invalid details are identified, wait for the test to finish before rejecting the connection setup.
  9. Initiate a file drop:
    1. Self-initiation for file drop.
    2. Click the Next button.
    3. Self-certification status to determine success or failure status of the file.
    4. Click Next.
  10. Verify and approve self-certification:
    1. Enter any comments in the Comments field.
    2. Click Approve or Reject.
    3. The Task Reopen feature can be used to revisit previous steps, if needed.
  11. Promote the connection to the production environment:
    1. Click the IP Whitelist check box.
      Note: You will be prompted to confirm the IP whitelisting if:
      • Enable parameter is set to not true under SSP section. This is to ensure the partners’ IP is whitelisted at your end.
      • Enable parameter is set to true under SSP section. This is to ensure the partners’ IP is whitelisted at your RMZ Firewall and the partner connection is established to your local balance/SSP.
    2. Enter the partner's user ID in the User ID field.
    3. Specify the virtual root path, which is the first level of directory path to the mailbox.
    4. Specify the path to which file is to be dropped by the partner i in the Directory field.
    5. file path from which file is to be picked up by the partner in the Out Directory field.
    6. Select transfer type – binary or ASCII.
  12. Execute Move to Prod task:
    1. Click Start Task in the Status/Actions column to open the Set Up Data Flow window.
    2. The Select Data Flow template is displayed. It is pre-populated with values that were configured earlier.
    3. Click Next.
    4. Select the direction of the file – Inbound, Outbound, or Both.
    5. Click Next.
    6. In Doc Type, select the appropriate document type.
    7. Enter the file name pattern of the file which will be sent in the File Name field.
    8. In Select Rules, select the required rules and change values if needed.
    9. Click Finish.
  13. An email with connection details and login credentials is sent to the partner. The partner should use this information to verify the connection.