Instance Deployment: Deploying the MYOB Acumatica Customer Portal

The MYOB Acumatica Customer Portal is designed to be a site where your customers can view all the relevant information about their interactions with your company as a vendor and perform common activities online.

To give your customers limited access to your MYOB Acumatica instance, you deploy a Customer Portal instance connected to your MYOB Acumatica instance. The deployment procedure is mostly the same as the procedure for an MYOB Acumatica instance. For details, see Instance Deployment: General Information.

If you deploy a multitenant MYOB Acumatica instance, after you deploy the Customer Portal instance, you must specify the tenant that the Customer Portal users can access. For details, see Instance Deployment: To Specify the Tenant Available for Customer Portal Users.

Attention:

If you want different tenants to be available through the Customer Portal, you must deploy a Customer Portal instance for each tenant.

If you need to distribute the load of user requests to a Customer Portal instance, you can create a group of Customer Portal instances that will be used as a single instance. The system recognizes Customer Portal instances as an instance group if the instances contain the same group identifier in their configuration. To create an instance group, you can deploy two or more Customer Portal instances, connect each of them to the same database, and specify the group identifier for each instance in the corresponding web.config file. In the file, the PortalSiteID setting in the appSettings section contains the value of the group identifier. For details, see Instance Deployment: To Set Up a Group of Customer Portal Instances.

Tip:

By default, the CustomerPortal-1 value is specified as the PortalSiteID setting for each newly deployed Customer Portal instance.

The system shows the group identifier for a Customer Portal instance in the Portal ID box on the Portal Preferences (SP800000) form in the Customer Portal.