Partner data form

Use the following form to record data about a partner who uses a trading engine other than Axway Activator. You can use the information on the completed form to create a partner in the user interface.

When you are ready to add a partner, go to the partners area of the user interface, click Add a partner and then click Manually create a new partner.

Related topics

Trading engine

Field

Partner’s data

Product name

 

Version number

 

Identity

Fields followed by an asterisk represent required information in Activator.

Field

Partner’s data

Company name *

 

Routing ID *

One ID is required but the partner can have multiple IDs

 

Contact name *

 

Contact phone number *

 

Contact e-mail address *

 

Protocol

The partner’s preferred protocol for your community to send documents.

Protocol

Partner’s data

EDIINT AS2 (HTTP)

 

Secure e-mail (for partners who use mail clients such as Microsoft Outlook)

 

Other (FTP, file system, JMS, MQSeries). No packaging or security

 

ebXML

 

Transport details

The partner’s preferred transport for your community to send documents.

HTTP, email

Field

Partner’s data

HTTP

URL

 

HTTPS

URL

 

Authenticate SSL connection

Circle one:    yes    no

SMTP/POP

e-mail address

 

SMTP-to-SMTP

e-mail address

 

SMTP server name

 

Port (default 25)

 

Use SSL

Circle one:    yes    no

If use SSL is yes, the SSL port

 

FTP

Setting

Partner’s data

FTP server name

 

Port

 

Inbox

 

Pickup

 

User name

 

Password

 

Clients must use SSL to connect to this server

 

JMS

Setting

Partner’s data

JNDI URL

 

JNDI factory

 

JNDI user name

 

JNDI password

 

JMS queue

 

JMS connection factory

 

JMS user name

 

JMS password

 

MQSeries

Setting

Partner’s data

MQSeries server

 

Port (default 1414)

 

Queue name

 

Queue manager

 

Channel

 

Character set (default 819)

 

User name

 

Password

 

Preferences

Preference

Partner’s data

Preserve original filenames

 

If preserve original filenames is true, overwrite duplicate filenames

 

If preserve original filenames is true, sequentially number duplicate filenames

 

Generate unique filenames

 

Security details

The partner must provide a digital certificate to effect secure trading.

Field

Partner’s data

Sign documents

Circle one:    yes    no

Request acknowledgments

Circle one:    yes    no

Request signed acknowledgments

Circle one:    yes    no

If HTTP or HTTPS, request synchronous acknowledgments

Circle one:    yes    no

Message digest

Circle one:

    SHA1 (default)

    MD5

Encrypt documents (yes or no)

Circle one:    yes    no

Binary and XML documents

Field

Partner’s data

Partner trades binary documents

Circle one:    yes    no

Partner trades XML documents

Circle one:    yes    no

XML type

 

Sender XPath if custom XML type

 

Receiver XPath if custom XML type

 

Related Links