Before defining a hub, you must first complete these setup steps:
Define the utl_file_dir parameters (performed by a DBA)
Navigate to the Hub Definitions form from the XML Gateway Responsibility by selecting Setup > Define Hubs.
A hub is an integration point within your network (either your intranet or the internet). Hubs are typically used to route documents to and from trading partners. Oracle Exchange is an example of a hub. You may also decide to create a private hub within your intranet through which all your ERP systems communicate.
The Hub Definitions form is used to define the hub and the authorized users conducting business via the hub. The hub users entered in this form will appear on the Trading Partner Setup form.
Enter the Hub name.
Protocol Type is the communication protocol associated with the hub, such as SMTP or HTTP. Select a value from the seeded list of values. The description for the protocol type is displayed.
When protocol type is HTTP or HTTPS, protocol address is prompted.
Protocol Address is the complete URL (including service/servlet) where the Transport Agent will attempt to post the XML Document.
If the Protocol type is SMTP, the protocol address is an e-mail address.
Enter the user name of the trading partner conducting business via the hub.
Enter the password for this user. The encrypted password is stored in the database. The password is not echoed when it is entered. You will be prompted on the same field to confirm the password.
Enter the hub entity code for this user.
Hub Entity Code has the same function as the Source Trading Partner Location Code in the Trading Partner Setup form. It is the code found in the XML envelope to identify the source of the message.
If you are sending and receiving messages from a trading partner, you will have a mixture of your location codes and your trading partner's location codes depending on the direction of the message. For example, if you are sending messages out, the Source Trading Partner Location Code is your location code because you are the source of the XML message. If you are receiving messages, the Source Trading Partner Location Code is your trading partner's location code because they are the source of the XML message.
This code is examined for inbound messages during Trading Partner validation. When placed on an outbound message, the recipient will validate it as a valid source location code.
The Hub Entity Code is placed in the PARTY ID field in the XML Gateway envelope.