Field | Description |
Package | Package for which you want to change subscription information. You can change the package to another package if you do not already subscribe to or publish the new package. This restriction exists because you cannot both subscribe to and publish the same package. |
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 page. From this page 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. Note: When the publisher connects to the subscriber, the publisher uses its default certificate (specified on its Security Settings page). Make sure the port you specify here can accept that certificate. |
Local User Name | User as which the publisher will log into the subscriber. This user must belong to a user group that is assigned to the Replicators ACL. If you delete the user or change its association with the Replicators ACL, the publisher cannot send this package to the subscriber. |
Local Password | Password for the local user name. |
Notification E-mail | 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 already have automatic pull configured and want to turn it off, select No. Then go to the Automatic Pull E-mail field and delete the e-mail address there. If you want to configure your server for Automatic Pull, 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 E-mail | 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. |