MOR-PLN-095 Version 1 (WIP) Last Review Date: August, 2024
1. Boomi Atom Setup
1.2. Atom Software
what is it
- where does it come from
- Linking it to Boomi
1.3. Atom Infrastructure
To run the Arom software, we are using an Azure Windows VM.
| Field | Production Environment | Development Environment |
|---|---|---|
| URL (UI) | ||
| Account ID | ||
| Listener URL | TBC | TBC |
| Atom ID | bbe6b41c-47a7-442c-8bf1-ffd9d7c10a6f | 06eaddac-113b-497a-83e3-9aa641d199d3 |
| Atom FQDN | boomiciprod.cbcgroup.com.au | boomici.cbcgroup.com.au |
1.3.1. Virtual Machine
The Atom software runs on a Windows VM.
| DETAIL | PRODUCTION ENVIRONMENT | DEVELOPMENT ENVIRONMENT |
|---|---|---|
| Azure | ||
| Azure Resource | BoomiVMClientProd | BoomiVMClientIntergration |
| Azure Link | https://portal.azure.com/#@cbcgroup.com.au/resource/subscriptions/91c10c4d-4bb4-45bb-a0d3-0b660951bb00/resourceGroups/BOOMIVMCLIENTPROD_GROUP/providers/Microsoft.Compute/virtualMachines/BOOMIVMCLIENTPROD/overview (opens in a new tab) | https://portal.azure.com/#@cbcgroup.com.au/resource/subscriptions/91c10c4d-4bb4-45bb-a0d3-0b660951bb00/resourceGroups/RG-BOOMI/providers/Microsoft.Compute/virtualMachines/BOOMIVMCLIENTINTERGRATION/overview (opens in a new tab) |
| Azure VM SKU | Standard D2s v3 | Standard D2s v3 |
| Virtual Machine | ||
| Public IP Address | 52.255.60.29 | 4.198.72.252 |
| Custom Domain | boomiciprod.cbcgroup.com.au | boomici.cbcgroup.com.au |
Note: Peter Newhouse created the VM's.
1.3.1.1. Custom Domain
The custom domain names that are asscoiated with the Atom Virtual Machines are managed in the CBC Cloudflare platform.
2. Boomi Platform
2.1. Integration
2.1.4. Folder Structure
The Integration building view shows the Components that have been created within Boomi. Each Component is organised within a folder system.
| FOLDER | PURPOSE | NOTES |
|---|---|---|
| #COMMON | Holds Components that can be used in any integration, such as the error logging and alert email processes. | |
| #COMMON-CMMS | Holds Components that are relevant to CMMS, such as generic sub-processes, JSON profiles, and Operations. | |
| #COMMON-MEX | Holds Components that are relevant to MEX, such as generic sub-processes, JSON profiles, and Operations. | |
| #COMMON-SC | Holds Components that are relevant to ServiceChannel, such as generic sub-processes, JSON profiles, and Operations. | |
| %Sandbox | ||
| MEX-CMMS | Holds integration-specific Components, such as the main Processes, sub-processes, environment variables etc. | |
| SC-CMMS | Holds integration-specific Components, such as the main Processes, sub-processes, environment variables etc. |
Callout Editing Common Components can affect any/all integrations in the platform. Extreme care should be taken not to make breaking changes to components without careful consideration of all processes that use the Component.
Within each folder are subfolders for various component types present for that integration. Components should be placed in sub-folders, rather than the root integration folder.