BusinessObjects Enterprise XI Release 2

(1)

BusinessObjects Enterprise XI

Release 2

How to configure an Internet Information Services server as a

front end to a WebLogic application server

Overview

This document describes the process of configuring a Microsoft Internet Information Services (IIS) web server as a front end to a WebLogic Java Application server. The IIS server accepts requests for InfoView and forwards these requests to the WebLogic server using a WebLogic plug- in installed on the IIS server.

Introduction

This document describes the process of configuring a Microsoft IIS Web Server as a front end to your WebLogic Java Application server.

The IIS server accepts requests for InfoView and forwards these requests to your WebLogic server using a WebLogic plug-in installed on the IIS server.

Create the directory

The initial step in the process is to create a directory on the IIS server.

Here are the steps:

1. Ensure IIS is installed on some server.

2. Create a directory on the IIS server called <installation drive>:\IISredirect

3. The WebLogic plug-in for IIS consists of two files. (iisproxy.dll and iisforward.dll). Copy iisproxy.dll and iisforward.dll from the

<installation drive>:\bea\weblogic81\server\bin directory to the

<installation drive>:\IISredirect folder on the IIS server.

These DLL files are for the WebLogic plug-in for IIS. These files could also be located under <installation

drive>:\bea\weblogic81\server\plugin\win.

4. Create a blank text file in the <installation drive>:\ IISredirect directory. Name it iisproxy.ini.

5. Open iisproxy.ini. Copy the following lines into the file:

WebLogicHost=hostname or FQDN of Weblogic server WebLogicPort=7001 or whatever port weblogic is using WlForwardPath=/businessobjects/enterprise115/desktoplaunch ConnectTimeoutSecs=10

ConnectRetrySecs=10 WLIOTimeoutSecs=2700

WLTempDir= Install Drive:\IISredirect

Note: These settings are case sensitive. For debugging purposes, add Debug=ON to the iisproxy.ini. The log file is located in <installation drive>:\IISredirect.

(3)

Figure 1 – Locating the WebLogic plug-in files

6. Save and close the iisproxy.ini file.

7. Give the NETWORK SERVICE user Full Control on the <installation drive>:\IISredirect folder.

8. Right-click the IISredirect folder > click the Security tab.

9. Add the NETWORK SERVICE user and configure permissions as in Figure 2.

(4)

Figure 2 – Configuring NETWORK SERVICE permissions

10. Create a new folder in <installation drive>:\IISredirect. Name it _wl_proxy.

11. Configure IIS to recognize the iisproxy.dll and iisforward.dll files.

12. Open IIS Manager. Expand the local computer node.

(5)

Figure 3 – Creating the _wl_proxy folder

(6)

Figure 4 – Opening IIS Manager

(7)

Figure 5 – Expanding the local computer node

Set the account under which the Default Application Pool runs

The account to run the Default Application Pool must now be created.

Here are the steps:

1. Right-click the Application Pools folder > click Properties.

2. Click the Identity tab.

3. Click NETWORK SERVICE from the Application pool identity security account dropdown list.

4. Click Apply > Yes. This confirms that the application is to run as a NETWORK SERVICE.

5. Click OK.

(8)

Figure 6 – Setting the NETWORK SERVICE account

Configure the ISAPI redirect filter

With the account created, configure the redirect filter.

Here are the steps:

1. Expand the Web Sites folder.

2. Right-click the Default web site icon. Click Properties.

3. Click the Home Directory tab > Configuration button. The Application Configuration dialog box appears.

(9)

Figure 7 – Configuring the Default Web Site properties

4. Click Add. The Add/Edit Application Extension Mapping dialog box appears.

5. Click Browse. Navigate to the <installation drive>:\IISredirect

directory. Click iisproxy.dll.

Figure 8 – Setting the Application Extension mapping

(10)

6. Type “.wlforward” in the Extension box.

7. Clear the Script engine and Verify that file exists options. Click OK.

8. Click OK again to close the Application Configuration box and return to the Default Web Site Properties dialog box.

9. Change the Execute permissions to Scripts and Executables.

Figure 9 – Changing the Execute permissions

10. Click the ISAPI Filters tab > Add. Type “iisforward” for the filter name.

11. Click Browse > <installation drive>:\IISredirect\iisforward.dll as the executable.

(11)

Figure 10 – Setting iisforward.dll as the executable

12. Click OK > Apply on Default Web Site Properties.

13. Click the Directory Security tab.

14. Click Edit > Authentication and Access Control.

15. Click the Enable Anonymous access option.

16. Click OK > OK on the Default Web Site properties.

(12)

Figure 11 – Setting the authentication method

Configure the Web Services Extensions

To configure the Web Services Extensions, use the following steps:

1. Click the Web Services Extension folder.

2. Click Add a new web service extension.

(13)

Figure 12 – Adding a web service extension

3. Type “WebLogic IIS Proxy Plug-ins” in the Extension name box.

4. Click Add > Browse.

5. Navigate to the iisforward.dll file in the <installation drive>:\IISredirect directory. Click Open > OK to add it.

6. Click Add > Browse. Navigate to the iisproxy.dll file in <installation directory>:\IISredirect.

7. Click the Allowed option for the Set extension status. Click OK.

8. Restart IIS to load the iisproxy.dll.

9. Click Start > Administrative Tools > Services.

10. Right-click the IIS Admin Service > click Restart.

(14)

Figure 13 – Logging on the Services

(15)

Figure 14 – Restarting IIS Admin Service

(16)

Connect to InfoView

Connect to InfoView using a web browser to the IIS server. Use the following URL:

http://<IISservername>/businessobjects/enterprise115/desktoplaunch

Figure 15 – Successfully connecting to InfoView using the new connection

Finding more information

For more information and resources, refer to the product documentation and visit the support area of the web site at

http://www.businessobjects.com/

BusinessObjects Enterprise XI Release 2