HomePowerServer Web | PowerServer MobileAppeon Documentation Center

Configuring IIS with WebSphere

The Default Web Site of the IIS server is used as examples in this section. You can choose another existing Web site, or create a new Web site.

Installing PowerServer Web Component to the IIS Web root

Run the PowerServer setup program and install PowerServer Web Component to the Web root of the IIS Web site, for example, the Web root for the Default Web site is C:\Inetpub\wwwroot.

If you have installed PowerServer Web Component to another location, then you should copy the entire "appeon" folder from the installation directory of PowerServer Web Component to the IIS Web root.

Installing the redirector plug-in

Since IIS works on the Windows platform only, you must get redirector plug-ins from WebSphere running on Windows (not UNIX or Linux). For example, if you plan to use IIS as the Web server while PowerServer is installed to WebSphere on Sun Solaris, you must copy the redirector plug-in from WebSphere on Windows to the IIS Web server.

  1. Copy the iisWASPlugin_http.dll file from the %WAS_HOME%\bin\ folder to any location of the IIS Web server, for example, C:\Inetpub\wwwroot\AppeonWeb. If IIS and WebSphere reside on the same machine, you do not need to copy the file.

  2. Open Control Panel | Administrative Tools | Internet Service Manager.

  3. Right click the Default Web Site and select New | Virtual Directory from the popup menu.

  4. Create a virtual directory using the name "sePlugins" and set the virtual directory to the folder where the iisWASPlugin_http.dll file is located.

    For example,

    Alias: sePlugins

    Directory: C:\Inetpub\wwwroot\AppeonWeb

  5. Enable Read, Run script, and Execute permissions on the virtual directory.

  6. Right click Default Web Site and select Properties from the popup menu.

  7. On the ISAPI Filters tab, click Add, and install iisWASPlugin_http.dll as an ISAPI filter. Filters are invoked in the listed order. We recommend that you install iisWASPlugin_http.dll first in the list. Click OK.

    For example,

    Filter Name: appeon_filter

    Executable: C:\Inetpub\wwwroot\AppeonWeb\iisWASPlugin_http.dll

  8. Restart IIS for the new configuration to take effect. Go to the ISAPI Filters tab and verify that iisWASPlugin_http.dll has been loaded successfully (indicated by a green arrow pointing upward while a red arrow pointing downward indicates that the DLL file was not successfully loaded).

Adding virtual host in WebSphere console

  1. Click Environment > Virtual Host in the navigation tree of the WebSphere Administrative Console.

  2. Click the New button in the page that displays.

  3. Input the IP address of the Web server in the Host Name field and port number in the Port field.

  4. Click Environment > Update Web Server Plug-in in the console navigation tree.

  5. Click OK to update the Web server plug-in.

  6. Save the new configuration and restart the WebSphere server.

Configuring the plugin-cfg.xml file

Copy the plugin-cfg.xml file from the %WAS_HOME%\config\cells\ folder to the virtual directory and modify the following directives according to the PowerServer\WebSphere environment:

Configure the log file location. For example:

<Log LogLevel="Error" Name="C:/Inetpub/wwwroot/_vti_log/http_plugin.log"/>

Configure the IP address and port number of the PowerServer\WebSphere. For example: 

<Transport Hostname="192.0.0.39" Port="9080" Protocol="http"/>
<Transport Hostname="192.0.0.39" Port="9443" Protocol="https">
    <Property name="keyring" value="C:/Websphere/AppServer/etc/plugin-key.kdb"/>
     <Property name="stashfile" value="C:/Websphere/AppServer/etc/plugin-key.sth"/>
</Transport>

Configure the context path. For example:

<UriGroup Name="server1_Cluster_URIs">
    <Uri Name="/servlet/*"/>
    <Uri Name="/AEM/*"/>
</UriGroup>

Creating the registry key

In the registry of the IIS Web server, locate the "HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Application Server\5.1.0.0" key (if any of these are missing, create them), add the "Plugin Config" string and set the value to the directory of the plugin-cfg.xml file.

Additional configuration for IIS

  1. Activate ISAPI:

    • Open the IIS manager.

    • Click Web Service Extensions on the left side of IIS manager.

    • Select All Unknown ISAPI extensions on the right of the window and click the Allow button on the left.

  2. Add a MIME type for loading the DataWindow files:

    • Right click Default Web Site and select Properties from the popup menu.

    • Select the HTTP Header tab and click the MIME Types button.

    • Click the New button to add a MIME type.

      For example:

      Extension: *

      MIME type: application/octet-stream

    • Restart IIS for the new settings to take effect.

Configuring for DataWindow Data Cache for IIS

Under the installation directory of PowerServer Web Component (for example, C:\Inetpub\wwwroot\appeon), there is an IISSupport folder.

  1. Copy the appeoncache.conf file from the IISSupport\conf folder and the AppDataBuf.dll file from the IISSupport\modules folder to the same folder, for example, C:\Inetpub\scripts.

  2. If necessary, adjust the cache size in the appeoncache.conf file (The unit is MB).

  3. Open Control Panel | Administrative Tools | Internet Information Services Manager.

  4. Right click Default Web Site and select Properties from the popup menu.

  5. On the ISAPI Filters tab, click Add, and install AppDataBuf.dll as an ISAPI filter. Click OK.

    For example,

    Filter name: appeon_cache

    Executable: C:\Inetpub\scripts\AppDataBuf.dll

  6. On the Service tab, select the Run WWW service in IIS 5.0 isolation mode option.

  7. Restart IIS for the new configuration to take effect.

Prev  Up  Next
Configuring IIS with WebLogic  Home  Configuring Apache