Thursday, 7 April 2016

Installing OnCommand Workflow Automation 3.1 (on Windows 2008 R2)

Useful links:

Hardware and Basic Components

OS: Windows Server 2008 R2 Enterprise SP1*
*Alas, don’t have a licensed Windows Server 2012R2 in my lab
Hardware: 4 GB RAM (3 GB is the minimum) and 2 vCPU
Software: .NET Framework 3.5.1 feature (WCF Activation not installed)
Software: .NET 4.0 (dotNetFx40_Full_setup.exe - PowerShell 3.0 pre-req)
Software: PowerShell 3.0 (Windows Management Framework 3.0 / Windows6.1-KB2506143-x64.msu)
Browser: Chrome 44 + Adobe Flash 18** / IE 10 + Adobe Flash Player 21
**Flash Player is pre-installed in Google Chrome!
Local Admin User: LAB\WFA

(Optional) Installing VMware vSphere PowerCLI 6.3 on Windows 2008 R2

This is a simple double-click install. Double-click the exe - VMware-PowerCLI-6.3.0-3639347.exe - to install.
Note 1: If the PowerShell ExecutionPolicy is not set to RemoteSigned or less, the install will warn about this, use Set-ExecutionPolicy RemoteSigned (or Unsigned for less restriction).
Note 2: This installs .NET Framework 4.5 Full - it downloads it when you run the exe and reboots the machine!
Note 3: It also installs the VMware Remote Console Plug-in 5.1 - plugins for IE, Firefox, and Chrome.

Image: Installing VMware vSphere PowerCLI

(Optional) Installing the MySQL .NET connector on Windows 2008 R2

This is a simple double-click install. Double-click the msi - mysql-connector-net-6.9.8.msi - to install.

Installing OnCommand Workflow Automation 3.1

Note: Refer to the “OnCommand Workflow Automation 3.1: Installation and Setup Guide for Windows” for full instructions.

Logged in as LAB\WFA (note that the instructions do say log in to Windows using the default local administrator account, but many organizations will use disable this), you can either install WFA 3.1 interactively by right-clicking the WFA install executable and selecting “Run as administrator” and answering the prompts -

Image: Starting WFA 3.1 Interactive Installation
- or silent install via the DOS Administrator: Command Prompt (which is the method used here - partly because it’s much easier to document) as in the example below:

Image: Running WFA 3.1 Silent Installation

WFA-x64-v3.1.0.0.2P2-B3650164.exe /s /v"WFA_ADMIN_USERNAME=admin WFA_ADMIN_PASSWORD=YourPassword WFA_ADMIN_CONFIRM_PASSWORD=YourPassword WFA_INSTALL_SITE=lon WFA_INSTALL_ORGANIZATION=lab WFA_HTTP_PORT=80 WFA_HTTPS_PORT=443 WFA_ENABLE_HTTP=1 INSTALLDIR=\"C:\Program Files\NetApp\WFA\" DATABASEDIR=\"C:\Program Files\NetApp\WFA\Database\" /qn /l*v install.log"


Note 1: Replace YourPassword as required.
Note 2: The default ports 80 and 443 are specified here.
Note 3: WFA_ENABLE_HTTP was set to 1 above (the default is 0) which allows both HTTP and HTTPS for external communication.
Note 4: You’ll know the install is complete when the NetApp WFA Server service starts (see NA_WFA_SRV.exe in Windows Task Manager), and the install log should say:

MSI (s) (CC:C4) [14:17:46:786]: Product: OnCommand Workflow Automation -- Installation operation completed successfully.

What Comes Next?

Log into WFA via http(s)://WFA_Server_DNS_Name_or_IP and follow the WFA Setup Wizard (or not - can re-run Setup Wizard from the Administration menu later) - simples!

Image: WFA Setup Wizard
APPENDIX: Extending the Configuration

Storage Array(s): IP Address + User Name and Password (root or admin account credentials are recommended)
vSphere vCenter: IP Address + User Name and Password (needs VMware Power CLI)
OnCommand Unified Manager: IP Address + User Name and Password (read-only user is fine) - for Data Acquisition
Mail Server: Mail Host IP Address + User Name and Password (if required) - to send WFA notifications
AutoSupport: Proxy pass through (for HTTP/S), or Mail Host IP Address
Active Directory: IP Address + User Name and Password + Group name (for LDAP bind read-only)
SNMP: IP Address + Port - for WFA SNMP notifications
Syslog server: IP Address - send log data

No comments:

Post a Comment