For reasons of performance and scalability, it was necessary to move IIS to a server other than the BizTalk Server. The webservice to be hosted on IIS was responsible for sending messages to msmq. In that way a decoupled architecture was create with BizTalk reading from msmq.
The server was already installed with Windows Server 2012R2, IIS 8.5 and .Net Framework 4.5. What I needed to do, is configure the Windows Server roles and features. Start the Server Management. Choose add roles and features.
Windows Server roles:
- Application Server
- .Net Framework 4.5
- Distributed Transactions
- All except WS-Atomic Transactions
- TCP Port Sharing
- Windows Process Activation Support
- Http Activation
- TCP Activation
- File and Storage Services
- Storage Services
- WebServer
- WebServer
- Common Http Features
- All except Http Redirection and WebDav Publishing
- Health and Diagnostics
- Only Http Logging
- Performance
- Only Static Content Compression
- Security
- Only Request Filtering
- Application Development
- All except CGI
- Common Http Features
- WebServer
- Management Tools
- Install all options
Windows features:
- .Net Framework 3.5 Features
- .Net Framework 3.5
- Http Activation
- .Net Framework 4.5 Features
- .Net Framework 4.5
- Net 4.5
- WCF Services
- Http Activation
- TCP Activation
- TCP Port Sharing
- Message Queuing
- Message Queuing Services
- Message Queuing Server
- Directory Service Integration
- SMB 1.0
- TelNetClient
- User Interfaces and Infrastructure
- Graphical Management Tools
- Server Graphical Shell
- Windows Powershell
- Windows Powershell 4.0
- Windows Powershell 2.0 Engine
- Windows Powershell ISE
- Windows Process Activation Service
- Install all options
- WoW64 Support
- Message Queuing Services
Note: if you fail to install the Windows role for Http Activation, you might receive HTTP Error 404.3 – Not Found. The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.