IIS +WAS 整合3

5.    Enable read, run script, and execute permissions on the virtual directory.

6.    Right click the Web site where you want to install the plug-in 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. Appeon recommends 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.dllhas 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 WebSphere server.

IIS 6: 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 Appeon Server\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 Appeon Server\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>

IIS 6: 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 6

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 the 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 6

During the installation of Appeon Server Web Component, an IISSupport folder will be created under the directory that you specified in the installation program, by default the folder will be created in C:\Program Files\Appeon\WebComponent2013\appeon.

1.    Create an “appeon” folder under the Web root of IIS server (for example, C:\Inetpub\wwwroot), copy the IISSupport folder from the installation path to the created “appeon” folder (for example, C:\Inetpub\wwwroot\appeon).

2.    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

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

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

5.    Right click the Web site and select Properties from the popup menu.

6.    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

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

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

 

 

Installing, Updating, and Configuring WebSphere 8.5 and 8.5.5

Note:

Unless otherwise noted, all references to WebSphere version 8.5 are also applicable to WebSphere version 8.5.5.

Beginning with JD Edwards EnterpriseOne Tools Release 9.1 Update 2.3, the IBM WebSphere Application Server Release 8.5 is supported.

Beginning with JD Edwards EnterpriseOne Tools Release 9.1 Update 3.3, the IBM WebSphere Application Server Release 8.5.5 is supported. This fix pack can be installed as a new installation or an update.

Relative to WebSphere 7.0, with IBM WebSphere 8.5 the installation procedure has changed dramatically. You will now use the IBM Installation Manager as a central hub to manage the installation process. The IBM Installation Manager is designed to make the installation procedure much simpler and easier than in prior releases.

Additionally IBM WebSphere Application Server 8.5 supports SDK 1.6 as the basic configuration but with SDK 1.7 as an optional configuration. For JD Edwards EnterpriseOne, the implementation requires SDK 1.7 as the default run-time configuration for WebSphere Application Server 8.5. Therefore, after WebSphere Application Server is installed with the basic configuration, you MUST change the default SDK to 1.7.

This chapter describes these tasks:

Section 3.1, “Before You Begin”

Section 3.2, “Installing the IBM Installation Manager”

Section 3.3, “Installing an IBM WebSphere Application Server 8.5 or 8.5.5”

Section 3.4, “Creating a New Profile for WebSphere Application Server 8.5”

Section 3.5, “Installing the IBM HTTP Server 8.5”

Section 3.6, “Installing Web Server Plug-ins for IBM WebSphere Application Server”

Section 3.7, “Enabling SDK 7.0 on WebSphere Application Server 8.5”

Section 3.8, “Switching to SDK 7.0 on WebSphere Application Server 8.5”

Section 3.9, “Installing the WebSphere Customization Toolbox”

Section 3.10, “Installing or Updating to WebSphere 8.5 Fix Pack”

Section 3.11, “Configuring the IBM Web Server Plug-in”

Section 3.12, “Setting the HTTP Server Properties”

Section 3.13, “Manually Generating a Plug-in”

Section 3.14, “Manually Editing the HTTP Configuration File”

3.1 Before You Begin

Before you install WebSphere, you must first set up a local user account that is in the Administrative group and has these advanced user rights:

Act as part of operating system

Create a token object

Log on as a service

Replace a process level token

To set up a local user account with the above user rights, navigate to:

Control Panel > Administrative Tools > Local Security Policy > Local Policies > Users Rights Assignment

On User Rights Assignment, double-click one of the user rights, click Add, select a local user account from the list, and click OK. Repeat this process for the remaining user rights.

You should also download all the required software from the JD Edwards Update Center.

3.2 Installing the IBM Installation Manager

For all supported platforms, you must install the IBM Installation Manager before an IBM WebSphere Application Server can be installed. Follow the steps below to install the Installation Manager.

After you have downloaded and unzipped the IBM Installation Manager software, locate the install executable.

On Microsoft Windows 2008R2, you must right-click and select the Run as administrator option.

以下文章点击率最高

Loading…


发表评论

您的电子邮箱地址不会被公开。 必填项已用*标注