This article provides the prerequisites to be reviewed before the Syndication-Brand PXM deployment, setup, and use.
The following prerequisites are applicable in this context:
Pre-app deployment:
App deployment:
Post-app deployment:
Tenant and accounts creation
Accounts Setup
- PIM tenant creation: A PIM tenant must exist.
For the tenant creation or the required apps deployment, you must raise the service request via External Service Desk with the following details:
- Syndication Brand PXM is required
- ces-integration (latest version)
- recipient-mgmt (latest version)
- schd-bulk-edit (latest version)
-
Exchange account: Set up the new Exchange tenant for the respective PIM tenant and Syndication account.
-
Syndication account creation: Syndication account must be created.
The Implementation Engineers must have access to the Syndication accounts and PIM accounts in both environments.
Tenant setup
Set the User Interface and Policy ID in the tenant before configuring authentication settings.
Application deployment
App setup
The latest version of the recipient-mgmt, ces-integration and schd-bulk-edit apps must be deployed and subscribed to the tenant.
Authentication setup
Authentication process for Syndication in Brand PXM:
After deploying and subscribing to the app, run the script below to create Auth Setup and App Configuration.
post_deployment_integration_130326.zip
Ensure you refer to the README.html included in the post_deployment_integration_130326.zip file before executing the script.
-
POD level setup:
This will be a default setup. -
Tenant level setup:
Tenant-specific configuration must be overridden for the required service with client ID and client secret ID, and the ID value should be set according to the service account. This operation can be executed successfully by utilizing the provided script along with the client ID and client secret.
To view the client ID and secret, see View Account API Credentials.
The user should have access to the respective self-service admin account:
https://selfservice.qa.syndigo.com/admin
View account API credentials:
From selfservice/admin portal, fetch the client ID and the client secret.
- Search for the account.
- Click on View Account API Credentials. The Username and Secret will be the client ID and client secret.
Once the post_deployment_integration script has been executed successfully, Auth Service inside nodejs container has to be re-started using pm2 reload all command.
SSO configuration
Once all deployment steps are complete, enable SSO for the tenant.