Yes
Modifying Endpoints
Although endpoint settings don’t often require changes, you might need to modify them under certain circumstances. For example:
-
Customers move their data center, so you must change the IP address or host name.
-
Customers update their credentials, so you must change the user credentials in the endpoint configuration.
-
Customers change their file naming conventions and response timeout requirements, so you must change these configurations for the endpoint.
-
The downstream API that receives translated inbound data moves from one region to another, so you must change the endpoint URL.
To modify an endpoint:
-
Access the endpoint you want to modify from the endpoint owner’s page (the <host>, <partner>, or third-party page, depending on the endpoint).
-
Click Edit.
-
Modify the desired settings. What you can modify depends on the endpoint protocol and usage, as described in the following sections:
-
Click Save to save your changes.
-
On the confirmation window that opens, select the I understand the effects of these actions checkbox and then click Confirm.
Partner Manager displays a Deploy button next to the modified endpoint.
-
Click Deploy to keep the endpoint changes.
-
On the confirmation window that opens, select the I understand the effects of these actions checkbox and then click Confirm.
Partner Manager redeploys the endpoint and all message flows that use the endpoint.
If required, Partner Manager also automatically deploys the Mule runtime applications that Partner Manager uses. The deployment of Mule runtime applications can take up to five minutes or longer to complete, depending on how many runtime applications are affected.
AS2 Receive Endpoints
You can modify the following fields for an AS2 Receive from Partners endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Endpoint name |
Yes |
Description |
Yes |
Enforce security level and associated fields |
No |
AS2 Send Endpoints
You can modify the following fields for an AS2 Send to Partners endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Authentication type and associated fields |
No |
Connection timeout |
No |
Description |
No |
Encryption algorithm |
No |
Endpoint name |
No |
Filename pattern |
No |
<host> AS2 identifier |
No |
<host> keystore |
Yes |
Maximum retry attempts |
No |
MDN signature algorithm |
No |
Message subject |
No |
<partner> AS2 identifier |
No |
<partner> AS2 URL, except for changing |
No |
Request receipt |
No |
Respond to email address |
No |
Retry interval |
No |
Signature algorithm |
No |
FTP Receive Endpoints
You can modify the following fields for an FTP Receive from Partners or Source at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Archival path |
Yes |
Endpoint name |
Yes |
Description |
No |
File name pattern |
Yes |
Host |
Yes |
Password |
Yes |
Polling frequency |
Yes |
Port |
Yes |
Character encoding override |
Yes |
Size check wait time |
Yes |
Source path |
Yes |
Username |
Yes |
FTP Send Endpoints
You can modify the following fields for an FTP Send to Partners or Target at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Description |
No |
Endpoint name |
No |
File name pattern |
No |
Host |
No |
Password |
Yes |
Port |
No |
Target path |
No |
Username |
Yes |
SFTP Receive Endpoints
You can modify the following fields for an SFTP Receive from Partners or Source at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Endpoint name |
Yes |
Description |
No |
Host |
Yes |
Port |
Yes |
Character encoding override |
Yes |
Authentication type |
Yes |
Username |
Yes |
Password |
Yes |
SSH |
Yes |
Source path |
Yes |
Polling frequency |
Yes |
Size check wait time |
Yes |
File name pattern |
Yes |
Archival path |
Yes |
SFTP Send Endpoints
You can modify the following fields for an SFTP Send to Partners or Target at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Endpoint name |
No |
Description |
No |
File name pattern |
No |
Host |
No |
Port |
No |
Authentication type |
Yes |
Username |
Yes |
Password |
Yes |
SSH |
Yes |
Target path |
No |
Filename pattern |
No |
HTTP Receive Endpoints
You can modify the following fields for an HTTP Receive from Partners or Source at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Connection idle timeout (in milliseconds) |
Yes |
Description |
Yes |
Endpoint name |
Yes |
Manage with API Manager and API Auto discovery ID |
Yes |
HTTP Send Endpoints
You can modify the following fields for an HTTP Send to Partners or Target at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Authentication type and associated fields |
|
Endpoint name |
No |
Description |
No |
URL |
No |
Response timeout (in milliseconds) |
No |
HTTPS Receive Endpoints
You can modify the following fields for an HTTPS Receive from Partners or Source at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Authentication type and associated fields |
Yes |
Connection idle timeout (in milliseconds) |
Yes |
Credentials |
Yes |
Description |
Yes |
Endpoint name |
Yes |
Manage with API Manager and API Auto discovery ID |
Yes |
HTTPS Send Endpoints
You can modify the following fields for an HTTPS Send to Partners or Target at Host endpoint:
Field | Redeploys the Runtime Application for the Endpoint |
---|---|
Authentication type and associated fields |
Yes |
Certificate |
Yes |
Description |
No |
Endpoint name |
No |
Response timeout (in milliseconds) |
No |
URL |
No |