Event messages for PEM Partner Provisioner
PEM Partner Repository sends and resends provisioning or testing requests to PEM Partner Provisioner, which responds to that request. On receiving the response from PEM Partner Provisioner, PEM Partner Repository performs the appropriate action based on the status of the provisioning or testing request.
For example, when a partner configures a protocol such as FTP, FTPS, or SFTP that needs to be
provisioned on an external system such as Sterling File Gateway, the Partner
Repository sends a provisioning request to PEM Partner Provisioner. The PEM Partner Provisioner in turn sends a response to PEM Partner Repository
indicating the status of the event message, whether successful or failed.
Tip: PEM Partner Provisioner can concurrently process a maximum of 10 event request
messages.
In PEM Partner Repository, the protocol configurations traverse through various
statuses. When a provisioning or testing request moves to a particular status, the PEM Partner Repository triggers an API call and raises the appropriate event based on the status
and configuration type. The following table provides the event type that is raised based on the
action and configuration type:
| Action | Protocol Configuration | Configuration Type | Event Type |
|---|---|---|---|
| startProvisionTestConfig | Inbound Push, Inbound Pull, Outbound Push, or Outbound Pull | Test | Provisioning Request |
| startProvisionProdConfig | Inbound Push, Inbound Pull, Outbound Push, or Outbound Pull | Production | Provisioning Request |
| startTestingTestConfig | Inbound Pull or Outbound Push | Test | Testing Request |
By default, the PEM Partner Repository event and REST API packages are set to
INFO log level. You can modify the default log level value.Warning: Suppressing either the event or REST API logs reduces the visibility into the processing of events
as UI is not present for event processing. However, suppressing the event logs does not affect the
functionality of PEM Partner Repository.