Installation
The installation process is an important milestone in the delivery process. Mind that non-standard infrastructure requirements and architecture should be reviewed with WorkFusion Lead Delivery Managers before any installation.
SPA Installation
Below is a common flow for the Intelligent Automation Cloud installation:
Define infrastructure requirements. It is usually done by Delivery Manager with the help of Senior RPA Developer (Solution Architect) or Senior MLE based on the scope and timeline. Refer to the standard build in the Plan infrastructure capacity section, note the difference between the Dev and Prod environments.
For the On-premise installation:
- Checklist coordination: Once requirements are clear they are communicated to Customer IT. The latter reverts with provisioned infra via Checklist filled in with actual data on infra.
- DM verifies the checklist:
- If some components don't have required specification it's essential to communicate how crucial it is to run WF product on required infra; otherwise it may lead to additional risks, non-stable and non-resilient environment which will dramatically affect development process, site-reliability and customer success as the result
- If all requirements are met DM creates a ticket for Installation team to plan installation. For on-premise installation IT person from customer end and his timezone are required to coordinate timing for installation.
Agree on installation support approach:
- Customer gives the WF/Partner team a direct access (for example, SSH) to instances, the WF/Partner team installs components thyself.
- The WF/Partner team sets up WebEx sessions, the Customer team gives remote control, installation is done by the WF/Partner team, Customer just observes.
- The WF/Partner team sets up WebEx sessions, the Customer team has control and perform installation according to the installation process with the WF/Partner team supervising the process.
For the Cloud installation, a ticket is raised in the Partner PS Support portal with the following details:
- Customer
- Project (usually the name of the use case)
- Due date
- Defined Infrastructure from #1
- For Cloud based installations, it's obligatory to make sure that no personal or sensitive data is hosted on the WorkFusion managed Cloud, for example, for POCs. Otherwise, choose the nn-prem installation.
Licenses are provided to the Installation team by WF IT once the Licence Agreement is signed:
- For APP, it's provided on the first day of installation. The license validity is defined in the License Agreement.
- For OCR License, tied to the actual server after the OCR service was installed on it. A Jira ticket is raised by DM in relation to Installation request, for example, via the Partner PS Support portal:
- Number of pages
- Supported languages (basic, CJK, all)
- Customer name
- License type (Prod or non-Prod)
- The WorkFusion Analytics License requested by DM via Partner PS Support. The required information:
- Customer name
- Project name
DM tracks the installation process and helps remove impediments if any.
Final stage of installation are post-installation health checks that are applied to confirm that everything is set up properly.
Once the installation is completed, it's transferred to support with all required information on the servers, so that in case of need, the Support team may refer to it. See the completed installation example below:
Value
Account Manager
<Name>
Delivery Manager
<Name>
Installation Engineer
<Name>
Installation JIRA Ticket
Link to JIRA
Product version For example, 9.1 or 8.5.3 Deployment type Prod Env checklist
Config.yml
Manifest.yml
OCR license
BI Server license
BI Desktop license
Start Date
End date
| Purpose | Name (DNS entries) | IP address | CPU | RAM | Disk Space | OS |
|---|---|---|---|---|---|---|
| Control Tower | wfapp-aaa.bbb.com | XX.XX.XXX.XXX | 8 | 32 | 250 GB | RHEL 7.3 |
| DB server | wfdb-aaa.bbb.com | XX.XX.XXX.XXX | 8 | 16 | 1 TB | RHEL 7.3 |
| OCR server | wfocr-aaa.bbb.com | XX.XX.XXX.XXX | 8 | 32 | 250 GB | RHEL 7.3 |
| VDS Cluster (Master + NFS) | wfml-aaa.bbb.com | XX.XX.XXX.XXX | 32 | 128 | 2 TB | RHEL 7.3 |
| VDS Slave 1 | wfmls1-aaa.bbb.com | XX.XX.XXX.XXX | 16 | 64 | 250 GB | RHEL 7.3 |
| АPM server | wfapm-aaa.bbb.com | XX.XX.XXX.XXX | 2 | 4 | 100 GB | RHEL 7.3 |
| BI server | wfbi-aaa.bbb.com | XX.XX.XXX.XXX | 4 | 16 | 100 GB | Windows 2012 R2 |
| RPA server | wfrpa1-aaa.bbb.com | XX.XX.XXX.XXX | 8 | 16 | 250 GB | Windows 2012 R2 |
Business Edition as development environment
In addition to the server installation, it is required for the development team to have Business Edition installed on their local machines as the development environment for the non-commercial usage. To get it, do as follows:
- Get the latest Business Edition.
- Request a Pro license via Partner PS Support.
Besides Business Edition, it is strongly recommended to install several other tools on developers' machines.