...

...

1 - Infrastructure

...

• Provision infrastructure account (see: coming soon...)
• Provision URLs and SSL certificates for related URLs (see: coming soon...)

2 - Products / Components

...

• Deploy the Maestrano stack (Nex!, MnoHub, Connec!, Impac!, etc.) (see: coming soon...)

• Activate / Deactivate features - admin dashboard / KPIs & Alerting / etc. (see: coming soon...)

• Deploy customised express (see: /wiki/spaces/EN/pages/59539661)
• Give admin rights to relevant users, on the platform (using active_admin) and on the tenant (using the admin dashboard) -  (see: coming soon...)
• Create a maestrano account with admin rights for each tenant / express: support@maestrano.com (credentials only accessible by Maestrano Support Team)

3 - Applications

...

• Check that the application is managed by developers.maestrano.com
• Check the type of integration (Connec! - Connectors, Cloud - Connectors, Third Party Cloud Application, Hosted App) and see below specific elements needed and actions to take
• From developers.maestrano.com, link the application + default environment to the new marketplace (see: Configure and test your technical integration#2.3Linkanenvironmenttoamarketplace)
• From the platform's MNOHub, link the environment to the requested tenant(s)  (see: coming soon...)

3.1 - Connec! - Connectors

...

• Configure the connector using these developer keys (see: Renew and Install Xero certificates)

3.2 - Cloud - Connectors

...

• If on premise:
  • Add a new environment on developers.maestrano.com for this application (see: Configure and test your technical integration#2.1Createanenvironment)
  • Deploy connectors on Nex! specific instance (see: Deploying a Connector)

3.3 - Third party Cloud Applications

• Check that the application is managed from the developer platform / is multi-marketplace
• If not, contact application for them to start developer platform migration (see: How to migrate to the developer platform)

4 - Third Party Systems

4.1 - Performance monitoring

...

• Create / Set up a new account (APMs, Servers, and Synthetics) and invite admin/users (see: coming soon...)
• Configure threasholds, APDEX and alerts (see: coming soon...)

4.2 - Logging monitoring

...

• Create / Set up account for enterprise customer and invite admin/users
• Configure log drains (see: Setting up a log drain)
• Configure collectors (see: coming soon...)
• Configure alerts (see: coming soon...)

4.3 - Jobs monitoring

• Set up a Sidekiq interface for Connec! Jobs and Mnohub Jobs (see: coming soon...)
• Set up accounts for platform admins - c.f. 2 Products / Components

4.4 - Transaction emails system

The platform can support different types of emailing systems for transaction emails: services managing email templates (Mandrill/Sparkpost) or delivery focused services (Mailgun/SMTP).
In the former case, the template customisation is done at the service provider level. In the latter, it's done inside the express frontend.

...

• Create / Set up an account for enterprise customer and invite admin/users (see: /wiki/spaces/EN/pages/83689538)
• If email customisation is needed: provide access to edit templates or set up customisation

4.5 - Customer onboarding and support / Platform support

...

• Create Intercom account and set it up on MNOE (see: /wiki/spaces/EN/pages/89784324)
• Create a JIRA Service Desk project - if applicable - or update the existing one

4.6 - Payment Gateway

...

• Create / Set up account for enterprise customer and invite admin (see: coming soon...)

4.7 - Others

...

• Google Analytics
• OpenexchangeRates
• Pusher (may not be required if impac-angular is not used)

5 - (Optional) Data Migration

Applicable in the following case:

...