Pre-Installation Requirements
Specific software prerequisites and hardware requirements must be satisfied in order for the Metadata Service and Request Handler to install successfully. The installer programs for these components checks for the software prerequisites. If any prerequisite software is missing, the installer program lists the missing items and requests that they be installed. The installation will not proceed until all prerequisites are installed.
Hardware Requirements
Computers running the Metadata Service and Request Handler must meet the hardware requirements listed in the table below. These requirements take into account not only requirements for Duet components, but other applications on which Duet relies.
Duet Server components are now supported on 64-bit architecture. The hardware requirements are shown for both x86 and x64 scenarios. Note that the installation folders for both x86 and x64 Duet Server components are available within the Duet CD as follows: CD\Microsoft\Installation Files\OBA Server\x86 and CD\Microsoft\Installation Files\OBA Server\x64
Note: Duet does not support the IA64, Itanium-based 64-Bit operating system.
Table 1.1: Microsoft Server Components Hardware Requirements 32-bit Architecture
Requirements | Minimum | Recommended |
Processor | Intel Xeon Dual-core | Intel Pentium Xeon Dual-Proc (4 logical CPUs) or greater |
Processor speed | 3.20 GHz | 3.20 GHz or greater |
Random access memory (RAM) | 1 GB | 1 GB or greater |
Hard disk capacity | 30 GB primary, with a minimum of 4 GB of free space | 30 GB primary, with a minimum of 4 GB of free space or greater |
File system | NTFS | NTFS |
Table 1.2: Microsoft Server Components Hardware Requirements 64-bit Architecture
Requirements | Minimum | Recommended |
Processor | Intel Xeon Dual-core x-64 architecture-based computer | Intel Pentium Xeon Dual-Proc (4 logical CPUs) or greater x-64 architecture-based computer |
Processor speed | 3.20 GHz | 3.20 GHz or greater |
Random access memory (RAM) | 1 GB | 1 GB or greater |
Hard disk capacity | 30 GB primary, with a minimum of 4 GB of free space | 30 GB primary, with a minimum of 4 GB of free space or greater |
File system | NTFS | NTFS |
Software Prerequisites
The installation setup program checks for the following software prerequisites:
· The Windows Server®™ 2003, Standard or Enterprise
(SP 2).
Make sure that Internet Information Services (IIS) 6.0 with ASP.NET is enabled.
(SP 2).
Make sure that Internet Information Services (IIS) 6.0 with ASP.NET is enabled.
The Microsoft Authorization Manager (AzMan) is required for the Duet Metadata Service component. AzMan is automatically installed with the 32-bit version of Windows Server 2003 but must be manually installed when using the Windows Server 2003 64-bit version.
· The Microsoft® .NET Framework, Version 3.0, Service Pack 1
· Microsoft® SQL Server™ 2005 Express, Service Pack 2 (SP 2) for 32-bit Duet server only. Microsoft SQL Server® 2005 Enterprise
Note: The SQL Server software prerequisite is for the Duet Metadata Service only
Other Installation Requirements
Some constraints are imposed by Duet components or by security requirements associated with their use. For this reason, deployments of the Metadata Service and Request Handler have additional installation requirements.
· Server components must be installed on computers with hard drives that are formatted with the NTFS file system. Some server components are not supported on a FAT32 file system.
· The Request Handler Service installation requires the use of an instance of Microsoft Exchange Server 2003 Enterprise Edition, Service Pack 2 (SP 2) or Exchange Server 2007 Service Pack 1 (SP 1). For more information, see the Duet for Microsoft Office and SAP: Microsoft Administration Guide.
· The Request Handler can communicate with the Exchange Server instance configured for forms-based authentication or Windows authentication.
· The Request Handler installation wizard requires an Exchange Server name to be entered for the component. When installing the Request Handler on a computer with a non-English locale the Input Method Editor (IME) mode must be changed to English before entering the required Exchange Server name. There are two methods for changing the IME mode to English; the first method is shown in the steps that follow.
To change the IME mode in Windows XP:
1. Open Regional and Language Options in the Control Panel.
2. On the Language tab, under Text services and input languages, click Details.
3. Under Installed services, click Add.
4. In the Input language list, click English for the Input method Editor (IME).
5. Select the Keyboard Layout/IME check box, if multiple options are available, and then click a service in that list.
6. If Keyboard Layout/IME is the only type of text service available, click an option in that list.
To change the IME mode in Vista :
1. Open Regional and Language Options.
2. Click the Keyboards and Languages tab, and then click Change keyboards.
3. Under Installed services, click Add.
4. Double-click the English language you want to add, double-click the text services you want to add, select the text service options you want to add, and then click OK.
The second and simple method to change the IME mode to English is shown as follows:
1. For Simplified Chinese IME: Press the Shift key.
2. For Traditional Chinese IME: Press the Shift key.
3. For Japanese IME: Press the keyboard combination Alt + ~ keys.
4. For Korean IME: Press the right Alt key.
· Register an Exchange Event Sink with all Exchange Servers that you use with the Request Handler Service. Additionally, an event sink must be applied on all Exchange Servers where Duet users will receive new or forwarded control messages. This will stop any sensitive data from appearing when a control message is forwarded.
The Exchange Event Sink folder is found on the Duet DVD at the following location: Duet DVD | Microsoft | IT Administrator Files | Exchange Event Sink. Use the following steps to register the Exchange Event Sink:
1. Copy the complete Exchange Event Sink folder from the DVD to your Exchange Server, for example C:\ExchangeEventSink.
2. Open a command prompt window and type the following: %windir%\Microsoft.NET\Framework\v2.0.502727
In case you use a x64 Exchange Server, type the following: %windir%\Microsoft.NET\Framework64\ v2.0.502727
3. Register the ExchangeEventSink.dll by typing the following command at the prompt: regsvcs-fc C:\Exchange Event Sink\ExchangeEventSink.dll
4. Open Administrative Tools and then Component Services. In the Component Services dialog navigate to the following location: Component Services | computers | My Computer | COM+ Applications | ExchangeEventSink, and then right-click the ExchangeEventSink node and click Properties.
1. Click the Security tab and then remove the check from the Enforce access checks for this application checkbox. Click Apply.
2. Click the Identity tab and in the Account section, click This user: and then type the Exchange Administrator credentials. Note that this account must have administrator privileges on the System Mailbox. Click Apply.
3. Click the Activation tab and enter the path of the event sink folder in the Application Root Directory text box, C:\Exchange Event Sink
4. Add a Role, CreatorOwner, under the ExchangeEventSink node and add the Exchange Administrator to that role, if this user is not already added.
5. Download and install either the Microsoft Exchange Server 2003 Software Development Kit or Microsoft Exchange Server 2007 Software Development Kit, depending on which Exchange Server you have. You will need both the regevent.vbs and regevent.cmd files, available in the SDKs to register an event sink.
Install the Microsoft Exchange Server 2003 Software Development Kit Documentation and Samples at: http://www.microsoft.com/downloads/details.aspx?FamilyID=5CA18D40-5A37-4A20-94AE-6A6CF6CB846D&displaylang=en
Install the Microsoft Exchange Server 2007 Software Development Kit at: http://www.microsoft.com/downloads/details.aspx?familyid=7a44a56a-1dfd-4c26-b99a-1e680e914444&displaylang=en&tm
5. Locate the regevent.cmd under the SDK installation directory.
6. Run the regevent.cmd from the Exchange SDK.
7. A valid Exchange account must exist for the Request Handler to use.
Ensure that a valid Exchange account has been created for the Request Handler to use. You should test or validate this account by logging on to the account either by using Outlook Web Access or by using Microsoft Office Outlook® 2003 or Outlook 2007.
Determine the default domain for the Exchange Server:
A .Open the IIS Management Console on the Exchange Server.
B .View the properties for the Exchange virtual directory.
C .Select the Virtual Directory tab and note the domain name included in the Local Path text box. For example, it should look like this:
View the SMTP addresses for the user:
D. Open Active Directory User and Computers and then view the properties for the DuetAgent user account.
E. Click the E-Mail Address tab
If necessary, add a new SMTP address that matches the domain name found in the Exchange Server virtual directory.
Installation of the Metadata Service and Request Handler will fail if the MSDTC service is not running on the server computer that is hosting the installation. Before installing these server components, ensure that the MSDTC service is started on the host computer.
To verify whether the MSDTC service is running, follow these steps:
8. On the server computer hosting the installation, click Start, and then click Run.
9. In the Run dialog box, type services.msc and click OK.
10. In the Services dialog box, locate the service named Distributed Transaction Coordinator.
11. Make sure that the service is started; the Status and Startup Type fields must show Started and Automatic, respectively.
Metadata Service
The Metadata Service assists the transfer of application metadata from the SAP system to the Duet client computer. The Metadata Service is responsible for maintaining the metadata database for Duet. This relational database resides on a Microsoft SQL Server® 2005 Enterprise Edition or SQL Server Express Edition SP2. Note that the SQL Server Express Edition, included in the product DVD, is supported for the Duet Metadata Service but Microsoft recommends using the SQL Server 2005 Enterprise Edition SP2 in a production environment for redundancy and supportability.
Additionally, the Web Service metabase file must be configured to enable Kerberos-based Integrated Windows Authentication. See the following Microsoft Support Site: http://support.microsoft.com/db/215383 , titled "How to configure IIS to support both the Kerberos protocol and the NTLM protocol for network authentication".
Integrated Windows Authentication includes the Negotiate, Kerberos, and NTLM authentication methods. Negotiate, a wrapper for Kerberos Version 5 and NTLM, allows the client application to select the most appropriate security support provider for the situation. See the Microsoft Help and Support Site: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/523ae943-5e6a-4200-9103-9808baa00157.mspx?mfr=true for detailed information.
Kerberos Version 5 and NTLM authentication have the following restrictions or limitations:
· NTLM can get past a firewall, but is generally stopped by proxies because NTLM is connection-based, and proxies do not necessarily keep connections established.
· Kerberos Version 5 requires that the client have a direct connection to Active Directory®, although that is generally not the case in Internet scenarios.
· Kerberos Version 5 requires that both the client and the server have a trusted connection to a Key Distribution Center (KDC) and be Active Directory-compatible.
· Kerberos Version 5 requires service principal names (SPNs) for multiple worker processes. If your Web site uses multiple worker processes, you can use Kerberos authentication, but you must manually register service names.
The following list shows additional information, requirements, and tasks to use for implementing the Metadata Service.
· If used, the SQL Server 2005 Enterprise
See “Metadata Database” in the Duet for Microsoft Office and SAP: Microsoft Planning Guide for more information.
· Administrators must secure the communication between the Metadata Service and the SQL Server after the MDS Server is installed. To secure this communication, open the Web.config file and add Encrypt=True to the connection string for the following Web services: AzManService, ReadServerService, and ServiceProviderService.
When a user attaches any SSL certificate issued by their organization to the SQL Server instance on the SQL Server they must run the SQL instance with the Network Service. The administrator must give the permission to the Network Service to pick the certificate while sending for SQL Server encryption.
The administrator must download and install the Windows HTTP Services Certificate Configuration Tool from, http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=C42E27AC-3409-40E9-8667-C748E422833F. This tool must be installed on the SQL Server to setup the additional Network Service permissions. The Windows HTTP Service Certificate Configuration Tool enables HTTPS to work between the MDS and SQL Server. The tool is installed on the default path, %System Drive
After the administrator installs the tool, they must run the following command in a command prompt window: winhttpcertcfg –g –c LOCAL_MACHINE/MY –s Certsrv –a ~Network Service
· Authorization Manager (AzMan) allows the Metadata Service to manage all metadata related permissions. AzMan must be set up for the Metadata Service.See the "Configuring Metadata Service Security using Authorization Manager (AzMan)" section for more information.
· Microsoft Internet Information Services (IIS) 6.0 and ASP.NET enabled in the Server Extensions node are used for hosting the Metadata Read Service Provider and AzMan Web services. Both instances must be installed and running prior to installing the Metadata Service.
· The Metadata Service relies on Active Directory 2000 directory service to establish Microsoft Windows authentication. Active Directory can then verify users and their access privileges regarding various Duet resources contained in the metadata.
· The Microsoft .NET Framework 3.0 Service Pack 1, must be installed and running on the server computer that hosts the Metadata Service.
· The Distributed Transaction Coordinator (MSDTC) service must be installed and running on the server computer that hosts the Metadata Service. See the "Other Installation Requirements" section for details.
· The Duet instance of SQL Server now hosts a Metadata Service database that contains all of the metadata and authorization information. If it is needed, Administrators can use the Metadata Publishing tool to create new administrator users to the Duet system. Administrators can also use SOAP calls to configure additional permissions with the Duet AzMan Web Service. Note that this is normally not necessary.
· See the Duet for Microsoft Office and SAP: Microsoft Planning Guide, "Chapter 5: Installation of Duet Server Components", section "Installation Requirements"; sub-section “Other Requirements for Metadata Service” for more information.
Request Handler Service
The Duet Request Handler Service handles and routes SAP system requests to Outlook through the Microsoft Exchange Server 2003 or Exchange Server 2007. The Request Handler separates the user interface programming details of Microsoft Office 2003 or Microsoft Office 2007 applications from the SAP systems and also provides an accessible view of the SAP generated requests in Outlook.
· Verify that the Distributed Transaction Coordinator (MSDTC) service is running on the server computer that will host the Request Handler service.
· Create a valid Exchange Server account for each Request Handler instance. Note that the Exchange Server should be accessible during the Request Handler install as the setup will try to validate the Exchange account that is provided during installation.
Before installing the Request Handler, you must log on to the Exchange account that will be used by the Request Handler using Outlook Web Access or Office Outlook to configure the user account.
The Request Handler Web service is called by the SAP ItemHandler components. All of the permissions on this service should be configured accordingly to allow the ItemHandler to invoke the Web services.
The Request Handler Web service runs with the specific DuetAgent, (mailbox designated for LOB messaging) credentials through impersonation. If additional permissions are needed you can create them using Windows authentication, or basic password authentication combined with HTTPS protocol to avoid exposing data. Alternatively, employ client and server certificates for mutual authentication.
All DuetAgent accounts that you have are listed in the Web site configuration file under the
· If you are using or plan to use a hosted Exchange Server environment to work with the Request Handler you must make sure the mail ID attribute of the corporate account ID is set with the resource forest account mail ID. Note that you should always install the Request Handler service with the HTTPS mode in a hosted Exchange environment. A hosted Exchange environment is typically where a 3rd party provides mail services for your organization, or where your organization provides mail for another organization. A corporate account forest is the forest or domain where the user accounts reside and a resource forest account is where the Exchange Server resides.
If you plan to use a hosted Exchange Server environment with the Request Handler, you must use the following steps:
12. Create a user account without a mailbox in the account forest (forest2), this is the hosted domain.
13. Create a user account with the same name in the Exchange forest or resource forest (forest1), and link this account with the alias you created in forest2.
14. Set the attribute of the mail ID for the user account in forest2 with the mail ID of forest1 user account using either the user properties or set-mailbox cmdlet.
15. Provide the appropriate trust between forest1 and forest2, the account forest and resource forest, respectively.
For more details about setting up this Exchange environment, see the following links:
· http://technet.microsoft.com/en-us/library/bb124734(EXCHG.80).aspx (Connecting Forest Topologies)
· http://technet.microsoft.com/en-us/library/aa998031(EXCHG.80).aspx (How to Deploy Exchange 2007 in an Exchange Resource Forest Topology)
· http://technet.microsoft.com/en-us/library/aa997312(EXCHG.65).aspx Exchange Server 2003 (Using a Dedicated Exchange Forest
· http://technet.microsoft.com/en-us/library/bb124677(EXCHG.65).aspx Exchange Server 2003 (Planning to Deploy Exchange in a Multiple Forest Environment)
· http://technet.microsoft.com/en-us/library/bb123590(EXCHG.65).aspx (Synchronizing Multiple Exchange 2003 Forests)
· http://technet.microsoft.com/en-us/library/cc164330(EXCHG.65).aspx Exchange Server 2003 (Accept Mail for a Domain)
· http://technet.microsoft.com/en-us/library/aa998597(EXCHG.80).aspx (How to Deploy Exchange 2007 in a Cross-Forest Topology)
· http://technet.microsoft.com/en-us/library/aa998787.aspx Exchange Server 2003 (Granting Access to External Accounts)
· http://technet.microsoft.com/en-us/library/bb123546(EXCHG.80).aspx (Configuring Cross-Forest Connectors)
· http://technet.microsoft.com/en-us/library/bb123524(EXCHG.80).aspx (How to Create a Linked Mailbox)
· http://technet.microsoft.com/en-us/library/bb123981.aspx (using Set-Mailbox cmdlet to modify existing mailbox settings)
· Configure the Exchange Server 2003 or Exchange Server 2007 to receive requests through the WebDAV interface over the HTTPS protocol.
Note: The HTTPS protocol is required if the Forms Based authentication is used. The Integrated Windows authentication can also work over the HTTP protocol; however, the WebDAV interface must be allowed on the Exchange server first. See the section titled "Allowing WebDAV on the Exchange Server" in chapter 2, Installing Duet Components, for details.
The Request Handler installation program does much of the setup and configuration process for the Request Handler Web server, completing the following tasks:
· Creates the Web service and provides Windows authentication as the default security mode, specifying no anonymous access to the Web site.
· Runs the Request Handler Web service under Exchange Server user credentials applied to DuetAgent, as specified in the installation wizard.
Names the Web service: http[s]://HostName:PortNumber/RequestHandler/RequestHandler.asmx
· Names the virtual directory RequestHandler.
· Names the ASMX file RequestHandler.asmx.
· Creates performance counters to monitor performance of the Request Handler.
If it is needed later, the administrator can create performance counters to monitor Request Handler performance
Preparing the Host for Duet Components (SAP)
1. Configure Duet to work with your SAP system.
Duet can work with one or more SAP systems. Therefore, you must determine the SAP system to be configured for use with Duet.
1. Install SAP NetWeaver (Application Server Java) 7.0 SP15 or a later version, and apply the relevant SAP notes to it.
2. Set the size for messages.
3. Configure gateway to communicate with SAP systems.
4. Configure trust between the Duet host and your SAP system.
Gather the information that you must provide during installation
