Cloud Application Integration (On-Premises) : Administering Integration Server : Managing Packages : Copying Packages from One Server to Another : The Subscribing Server : Subscribing to a Package from a Subscribing Server : Requesting a Subscription to a Package from Another Server
Requesting a Subscription to a Package from Another Server
The following procedures describe how to request a subscription.
Note:  
The publishing server must be running at the time you add the subscription
To request a subscription to a package from another server
1. Open the Integration Server Administrator if it is not already open.
2. In the Packages menu of the Navigation panel, click Subscribing.
3. Click Subscribe to Remote Package.
4. Type the name of the package in the Package field. Be sure to type the name exactly as it is specified on the publishing server, using the same combination of upper- and lowercase characters.
5. Enter the information in the following fields to set up your request:
Field
Description
Publisher Alias
Alias assigned to the publisher. The alias definition tells the subscriber how to connect to the publishing server to register for a subscription. The alias contains connection information such as host name or IP address. If you have not already defined an alias for this publisher, click the link to go to the Remote Servers screen. From this screen you can set up an alias for the publisher. See Setting Up Aliases for Remote Integration Servers for more information.
Local Port
Port number on which the subscriber listens for the publisher to send the package. This setting determines whether the publisher uses HTTP or HTTPS.
Important:  
If you want the publisher to use SSL when sending the package to the subscriber, you must specify an HTTPS port here.
Local Password
Password for the local user name.
Notification Email
E-mail address to notify when the publishing server releases a package or a package is delivered.
Automatic Pull
Specifies whether the subscribing server is to automatically pull the package from the publisher when a new release becomes available.
If you select Yes, you must also specify the e-mail address of a user on an e-mail server to which the publishing server should send a service-invocation e-mail.
The subscribing server, through an e-mail port, periodically checks this e-mail address for a service-invocation e-mail. When the subscribing server processes the e-mail, it pulls the package.
The service invocation e-mail contains a call to a service that runs on the subscribing server and loads the package to the subscribing server's Inbound directory.
For automatic pull to work, you must set up an e-mail port to listen at the automatic pull address (described below).
For information about setting up an e-mail port, see Adding an E-Mail Port.
Automatic Pull Email
E-mail address to which the publishing server is to send a service-invocation e-mail when a new release of the package becomes available.
Use a different e-mail address for the notification and service-invocation e-mails. For example, send notification e-mails to package_notifications@mymailserver.com and service invocation e-mails to package_autopulls@mymailserver.com.
For automatic pull to work, you must set up an e-mail port to listen at this address.
For information about setting up an e-mail port, see Adding an E-Mail Port.
6. Click Start Subscription.
Important:  
If you request a subscription to a package that does not exist on the specified server, or if that server does not own the package (i.e., it is a subscriber of the package), you will receive an error message, and the publishing server does not process your subscription.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback