Sterling B2B Integrator - Configuration Prerequisites

You can create user accounts from the Administration menu.

1. Log in to Sterling B2B Integrator.
2. From the Administration Menu, select Accounts > User Accounts.
3. Next to Create a new Account, click Go!
4. In the New Account page, select the Authentication Type.
5. Enter the User ID and Password.
6. Confirm the Password.
7. Select the Policy.
8. Enter the Session Timeout.
9. Select the Accessibility.
10. Select the Dashboard Theme.
11. Click Next.
12. On the SSH Authorized User Key page, assign one or more public keys. Move the keys from the Available pane to the Assigned pane and click Next.
13. On the Groups page, assign groups of permissions. Move the group names from the Available pane to the Assigned pane and click Next.
14. On the Permissions page, assign individual permissions. Move the permissions from the Available pane to the Assigned pane and click Next.
    By default, the permissions associated with the groups that this user is assigned to are already selected.
15. On the User Information page, enter the Given Name.
16. Enter the Surname.
17. Enter the E-mail address.
18. Enter the Pager number.
19. Select the Preferred Language.
20. Enter the Manager ID.
21. Select the Identity.
22. Click Next.
23. Review the user account settings.
24. Click Finish.
    The user account is created and this message is displayed:

    The system update completed successfully.

    If you created an external user, log out of the system, and then log back in with the external user ID or account. The system authenticates the external user ID on the external LDAP server.

Use the File System adapter to collect (import) files from a file system into a business process and extract (export) files from a business process to a file system.

You must associate each EBICS Client user with the preconfigured EBClientOrderMetadata mailbox.

1. Log in to Sterling B2B Integrator.
2. From the Administration Menu , select Deployment > Mailboxes > Configuration.
3. Next to Create a new Mailbox, click Go!
4. In the Mailbox: Name page, select the parent mailbox in which the mailbox you are creating is embedded. You can type a partial name in the Filter by Name field and click the filter button for a filtered list.
   The root mailbox is denoted by a slash (/).
5. In the Name field, type a name for the mailbox you want to create.
   This name is used to identify the mailbox in the Application, for example, EBClientOrderMetadata.
6. Required. In the Description field, type a short description for the mailbox and click Next.
   Use this field to describe the mailbox. This field is not used by any other resource in the system.
7. In the Assign Groups page, use the arrows to add the groups to the Selected Groups list and click Next.
   All groups in the Selected Groups list will have permissions on this mailbox. Click the first double arrow to add all available groups to the Selected Groups list.
8. In the Filter by Name field, type a partial group name in the field and click the filter button for a filtered list.
9. In the Accounts menu, multiple groups can be added. No groups are required.
10. Use the arrows to add users to the Selected Users list and click Next.
    All users in the Selected Users list will have permissions on this mailbox. Click the double arrow to add all available users to the Selected Users list.
11. In the Filter by ID field, type a partial name in the field and click the filter button for a filtered list.

Enabling a schedule makes the schedule active and causes the associated activity to run according to the schedule settings. A schedule must be enabled in order to run.

1. Log in to Sterling B2B Integrator.
2. From the Administration Menu, select Deployment > Schedules.
3. Use Search or List to locate the MailboxEvaluateAllAutomaticRulesSubMin schedule and click Go!
4. On the Schedules page, locate the MailboxEvaluateAllAutomaticRulesSubMin schedule and ensure that the check box in the Enabled column is selected.

You can create a self-signed certificate from the Administration menu.

1. Choose one of the following options:
   • If you use Sterling B2B Integrator, from the Administration Menu, select Trading Partner > Digital Certificates > System.
   • If you use the AS2 Edition, from the AS2 Administration menu, select Certificates.
2. Next to Create Self-signed Certificate, click Go!
3. Enter the Name of the self-signed certificate.
4. Enter the name of the Organization.
5. Select the Country or origin of the self-signed certificate.
6. Enter a contact e-mail address for the person responsible for certificates in the organization and then click Next.
7. Enter the Serial Number for the certificate.
   The serial number is the number you want to assign to the self-signed certificate.
8. Enter the Duration (number of days) that the self-signed certificate is valid.
9. Enter the IP addresses of the network interfaces you want to associate with the certificate as the SubjectAltName field.
10. Enter the DNS Names of the network interfaces you want to associate with the certificate as the SubjectAltName field.
11. Select the Key Length. Select one of the following key lengths:
    • 512
    • 1024
    • 2048

    Note: The key length 1024 provides a good balance between security, interoperability, and efficiency. The key length 2048 is the most secure, but also the slowest, and may not work with some applications. For information about defining EBICS-specific key lengths for electronic signature, encryption, and authentication, see EBICS Specification, version 2.5.

    Note: If you select the key length 512, you must check for JDK restrictions on the key length in the java.security file in the JDK. Else, protocol communication might fail during run time.
12. Select the Signing Algorithm.
    Note: You must use the SHA256withRSA signing algorithm for certificates used with EBICS transactions.
13. Select the Validate When Used option. Validation options are:
    • Validity – Verifies dates in the validity period of the certificate are still in effect. If the dates are not in effect, the certificate is not used.
      Note: Before you set a value to the validity period of the certificate, you must read and apply the best practice recommendations from the Microsoft PKI Quick Guide. For information about the best practice recommendations for using certificates, see http://www.windowsecurity.com/articles/Microsoft-PKI-Quick-Guide-Part3.html.
    • Auth Chain – Constructs a chain of trust for certificates that are not self-signed. If a chain of trust cannot be constructed using valid certificates, the certificate is not used. If the certificate is self-signed, this option verifies only the certificate signature.
14. Set the Certificate Signing Bit by selecting the check box.
15. Click Next.
16. Review the information about the self-signed certificate.
17. Click Finish.

Based on security policies at your site, Certificate Authority (CA) certificates in the Java Key Store (JKS) can also be checked in through the console.

1. Log in to Sterling B2B Integrator.
2. From the Administration Menu, select Trading Partner > Digital Certificates > CA.
3. Next to New Certificate, click Go!
4. Select a method to import certificates:

   Import method	Next Steps
   Import from JVM – Imports from the JKS keystore	Click Import from JVM. Accept the default password that appears in the password field and click Next. If the password field is empty, the system still uses the default password.
   Import from File – Imports certificates saved as a file on a local drive	Click Import from File. Enter the file name or click Browse to select a CA certificate file. Click Next. You may ignore the password that is displayed in the password field. There is no need to erase the entry.

   Available certificates are listed with a summary of identifying information. All certificates are selected by default.

5. Select the check boxes to the left of each entry to import the certificates.
6. For each certificate selected, accept the suggested Certificate Name or edit it based on your file naming conventions.
7. Select the Validate When Used option and click Next. Validation options are:
   • Validity – Verifies dates in the validity period of the certificate are still in effect. If the dates are not in effect, the certificate is not used.
   • Auth Chain – Attempts to construct a chain of trust for certificates that are not self-signed. If a chain of trust cannot be constructed using valid certificates, the certificate is not used. If the certificate is self-signed, this option verifies only the certificate signature.
8. If you receive a message stating that the certificate duplicates a certificate already in the database, enter Y or N to indicate whether to import the duplicate or not.

   This check is done on single certificates only. It does not take place when checking in one or more certificates from a file.

   Certificates are identified by SHA1 or SHA256 hash for purposes of determining duplicates. More than one copy of a certificate can be present in the database, since each certificate populates a different row and has a distinct object ID. The existing certificate is not overwritten.

9. Review the CA certificate information.
10. Click Finish.

You can check in a trusted system certificate from the Administration menu.

1. Choose one of the following options:
   • If you use Sterling B2B Integrator, from the Administration Menu, select Trading Partner > Digital Certificates > Trusted.
   • If you use the AS2 Edition, from the AS2 Administration Menu, select Certificates.
2. Next to New Certificate, click Go!
3. Enter the Filename or click Browse to select the file name of the trusted certificate and then click Next.
4. Enter the Certificate Name.
5. Verify the name of the trusted certificate you are checking in.
   For each certificate you selected, the Certificate Name field shows a suggested name, followed by a summary of the identifying information in the certificate. You can change the name based on your file naming conventions.
6. If you have more than one trusted certificate contained in the file you selected, select the check box to the left of each certificate to check in the certificate.
7. Select the Validate When Used option and click Next. Validation options are:
   • Validity – Verifies dates in the validity period of the certificate are still in effect. If the dates are not in effect, the certificate is not used.
   • Auth Chain – Attempts to construct a chain of trust for certificates that are not self-signed. If a chain of trust cannot be constructed using valid certificates, the certificate is not used. If the certificate is self-signed, this option verifies only the certificate signature.
   • CRL cache – Controls whether the Certificate Revocation List is consulted each time the system certificate is used.
8. Review the trusted certificate information.
9. Click Finish.

You can check in a key system certificate from the Administration menu.

1. Choose one of the following options:
   • If you use Sterling B2B Integrator, from the Administration Menu, select Trading Partner > Digital Certificates > System.
   • If you use the AS2 Edition, from the AS2 Administration menu, select Certificates.
2. Next to Key Certificate, click Go!
3. Enter the Certificate Name.
4. Enter the Private Key Password.
   This password is used to encrypt the private key.
5. Enter the Filename or click Browse to select the file name of the key certificate and click Next.
6. Select the Validate When Used option and click Next. Validation options are:
   • Validity – Verifies dates in the validity period of the certificate are still in effect. If the dates are not in effect, the certificate is not used.
   • Auth Chain – Constructs a chain of trust for certificates that are not self-signed. If a chain of trust cannot be constructed using valid certificates, the certificate is not used. If the certificate is self-signed, this option verifies only the certificate signature.
7. Review the key certificate information.
8. Click Finish.