BI商业智能>> biztalk-provisioner>> 返回
项目作者： anadimisra

项目描述 ：
Automated provisioner for BizTalk Server.
高级语言： PowerShell
项目地址: git://github.com/anadimisra/biztalk-provisioner.git
创建时间： 2017-07-24T03:12:21Z
项目社区：https://github.com/anadimisra/biztalk-provisioner
开源协议：MIT License
下载


biztalk-provisioner

Automated Vagrant + AWS provisioner for BizTalk Server.

How to run

Clone this repository, and cd to the biztalk-provisioner dir.

Run vagrant up or vagrant up --debug as needed, in a Powershell terminal.

:exclamation: Note the prerequisites below!

Prerequisites

The provisioner uses Vagrant, AWS, Powershell and Puppet; knowledge of these tools is assumed.

Additionally you need an AWS account.

The following environment variables need to be set and visible to Vagrant:

  1. VAGRANT_AWS_KEYPAIR_NAME: AWS keypair to use for authentication e.g aws_keypair.pem
  2. VAGRANT_AWS_KEY_PATH: Location of AWS keypair e.g /home/vish/.ssh/aws_keypair.pem
  3. VAGRANT_AWS_ACCESS_KEY
  4. VAGRANT_AWS_SECRET_KEY
  5. VAGRANT_AWS_SECURITY_GROUP: AWS Security group name (see "Port Requirements" below)
  6. VAGRANT_AWS_ELASTIC_IP: An elastic IP to allocate to the instance.

Why is an Elastic IP needed?

Several steps (e.g adding the remote server to TrustedHosts in Powershell) require knowledge of the IP address in advance.

Automation is simplified overall if the IP is predictable across provisioning runs.

Port Requirements

HTTP Basic authentication is used (for simplicity and as a first step) for communication over WinRM.

This means the AWS Security group should have at least port 5985 open for WinRM to work.

Additionally to connect over RDP to the running instance you need port 3389 open.

As an example, I have the following generic ports opened:

  1. 5985, 5986: for both HTTP and HTTPS based WinRM communication
  2. 3389: for RDP
  3. 137-139, 445: for future Samba connectivity

Notes

Needs to run on Windows + Powershell

Many steps of the Vagrantfile require Powershell, so do not run this Vagrantfile on Linux or Cygwin. Ideally you should use Powershell to run vagrant up.

Troubleshooting

Error: “Unencrypted traffic is currently disabled in the client configuration”

If you encounter this error during provisioning:

  1. [ec2-13-126-116-43.ap-south-1.compute.amazonaws.com] Connecting to remote server ec2-13-126-116-43.ap-south-1.compute.amazonaws.com failed with the
  2. following error message : The WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration. Change the client
  3. configuration and try the request again. For more information, see the about_Remote_Troubleshooting Help topic.

First enable Powershell Remoting on your client machine.

Note: For Powershell remoting to be configured correctly, your client machine’s Network Type needs to be set to Domain or Private.

Else you will encounter this error:

  1. PS C:\Users\savis\work\agilityroots\biztalk-provisioner> winrm quickconfig
  2. WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

Next, execute the following commands. This will enable Unencrypted Traffic. Note: only for development purposes.

reference.

  1. PS C:\Users\savis\work\agilityroots\biztalk-provisioner> cd WSMan:\
  2. PS WSMan:\> cd .\localhost\Client\
  3. PS WSMan:\localhost\Client> dir
  6.    WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Client
  8. Type            Name                           SourceOfValue   Value
  9. ----            ----                           -------------   -----
  10. System.String   NetworkDelayms                                 5000
  11. System.String   URLPrefix                                      wsman
  12. System.String   AllowUnencrypted                               false
  13. Container       Auth
  14. Container       DefaultPorts
  15. System.String   TrustedHosts                                   ec2-13-126-116-43.ap-south-1.compute.amazonaws.com
  18. PS WSMan:\localhost\Client> Set-Item .\AllowUnencrypted $true
  19. PS WSMan:\localhost\Client> dir
  22.    WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Client
  24. Type            Name                           SourceOfValue   Value
  25. ----            ----                           -------------   -----
  26. System.String   NetworkDelayms                                 5000
  27. System.String   URLPrefix                                      wsman
  28. System.String   AllowUnencrypted                               true
  29. Container       Auth
  30. Container       DefaultPorts
  31. System.String   TrustedHosts                                   ec2-13-126-116-43.ap-south-1.compute.amazonaws.com