Post-deployment tasks

There are tasks that must be completed after the local package has been deployed. This section describes these tasks.


	Task	Description
❑	Activate or reactivate the model.	See these topics in the ION documentation for information: Activating a data flow Activating workflow definitions Activating monitors Activating alarm templates Activating activation policies
❑	Connect > Enterprise Locations	Create credentials for the location. Download and install an Enterprise Connector on a tenant specific local (On Premises) system.
❑	Connect > Enterprise Connector connection points	If applicable, configure the connection parameters. Create and link PGP keys.
❑	Monitors&Workflows > Workflows	Users are considered tenant specific so they are not exported and imported. If you need users in your workflow definition distribution lists, you must add them. If API calls are configured, API calls need a Service Account for authentication. Service Accounts are considered tenant specific, so in the target tenant you must create a new Service Account. Or, you can use an existing account and apply it to the API call.
❑	Monitors&Workflows > Monitors	Users are considered tenant specific and are not exported and imported. If you need users in your workflow definition distribution lists, you must add them.
❑	Monitors&Workflows > Business Rules	Users are considered tenant specific and are not exported and imported. If you need users in your workflow definition distribution lists, you must add them.
❑	Configuration > Error Reporting	Configure email addresses. See the Receiving emails for exceptions topic in the ION documentation for information.
❑	Configuration > ION Service > Configuration Files > Certificate Store	Import trusted certificates.
❑	Configuration > ION Service > Configuration Files > E-mail Templates	Adjust any templates that include tenant specific email references. See the Customizing the layout for email notifications topic in the ION documentation for information.