AppCentral Environment Alignment
- This page is here only for archive purpose. All specfied tasks have been completed.
New environments for AppCentral specific development are now available. Please complete the following tasks to migrate AppCentral and Product environments.
AIP environment: Environments
- Update base URL for AIP
- Use IAM authority matching the environment to retrieve bearer token
- Use bearer token - instead of x-aptean-tenantId and x-aptean-apim in the header
- ATG subsmgmt based service accounts will not be supported for AppCentral based products
- Create Event Definitions in new environments
- New product names have been added to IAM
- Migrate IAM event definitions to Product ID - Aptean IAM (dc2e9ce0-7ea3-4fee-8bee-9e0573d0512c)
- Migrate AppCentral event definitions to Product ID - AppCentral (920a1de7-ab68-4c03-b4d8-89cb3a921957) for easier management
- Migrate Flowable event definitions to Product ID - Flowable (970a2a5a-77b1-4bfe-8971-d7624e781356)
- Use Product-level integration - instead of tenant - in each environment
- This change would eliminate need to create subscriptions when a tenant is onboarded
- Product-level Integration
- AIP team will migrate all data mapping from current stg to appcentral-aip-dev and appcentral-aip-tst
Track completion:
- AppCentral
- Ship
- M2M
- CRM
- EAM
- Flowable
- IAM
- Pay
- EDI
- AIP Staging
Notes:
- CRM uses profile info in configuration to identify tenant
- Following service tenant IDs provisioned as static in all environments:
- AppCentral - 0E73F11D-5DBC-4C64-BAF6-16F783AE6C62
- IAM - 6B42E5A8-D4D2-40D9-B41D-84BD9EE7D08E
- Pay - 2905DC76-20BF-4721-9026-0B988E1DAD4A
- EDI - 0635B1F9-EE34-4A99-B9BC-216E1F32C71E