Gopanel 1 9 2 – Manage Web Servers 1 8

Starting with modjk 1.2.6 for Apache 2.x and 1.2.19 for Apache 1.3, it's possible to exclude some URL/URI from jk processing by setting the env var no-jk, for example with the SetEnvIf Directive. You could use no-jk env var to fix problem with modalias or moduserdir directive when jk and alias/userdir URLs matches. If the requested file is not present in the server, the server should send an HTTP “404 Not Found” message back to the client. Put an HTML file (e.g., HelloWorld.html) in the same directory that the server is in. Run the server program. Determine the IP address of the host that is running the server (e.g., 128.238.251.26). If you cannot access the Integrated Solutions Console from the browser after changing the SSL protocols to TLS 1.2, the browser might not be configured to support the protocol or does not support the protocol. For information about configuring browsers to support TLS 1.2, see Configuring browsers to support Transport Layer Security (TLS) 1.2.

Gopanel 1 9 2 – Manage Web Servers 1 8 Bit
Gopanel 1 9 2 – Manage Web Servers 1 8 Free

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:

3.1 Before You Begin

Before you begin the installation of WebSphere 8.5 on UNIX systems, you should perform the steps in this section.

In WebSphere Application Server Version 8.5 information Center, review the section entitled: 'Preparing the operating system for product installation'. Update your system according to the requirements.
By default, the IBM WebSphere Application Server runs as root. However, it can also be run by using a non-root user ID. The non-root user can install WebSphere Application Server in both silent and interactive nonAdmin mode for full product installations and removals, incremental feature installations, and edition upgrades.
Non-administrator installations install an operational product
If some portion of an installation requires administrator privileges, Installation Manager provides an option so that the non-administrator can install an operational product without enabling the privileged option whenever possible.
Install Manager identifies root-only options
Installation Manager clearly identifies privileged options by disabling such option in the interface of the non-administrator.
- Open the install.ini from the Installation Manager directory
- Change the -accessRights from admin to nonadmin
Download all the required software from Oracle JD Edwards Update Center
- WebSphere Application Server Network Deployment - 3 Disk Images
- WebSphere Application Server Supplement - 3 Disk Images
- WebSphere Application Server SDK 1.7 - 3 Disk Images
Update the server with the latest OS patches.

3.2Installing 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 Install Packages, package selection, select the check box for the latest version of the IBM Installation Manager.
Click the Next button.
On Install Packages, review the International Program License Agreement and click the radio button to accept the terms if you want to continue with the installation.
Click the Next button.
On Install Packages, select a location for Installation Manager, enter an installation directory.
For example:
/u01/WebSphere85/InstallationManager/eclipse
On Install Packages, summary information, review the summary information and click the Install button to begin the installation.
On Install Packages, if you are ready to install using the IBM Installation Manager, click the Restart Installation Manager button.
After the Installation Manager is restarted, continue to the next section in this chapter entitled: Section 3.3, 'Installing an IBM WebSphere Application Server 8.5 or 8.5.5'.

3.3Installing an IBM WebSphere Application Server 8.5 or 8.5.5

IBM WebSphere Application Server (WAS) 8.5 is installed through the IBM Installation Manager. Fix Pack 8.5.5 can be installed as a new installation or an update. For purposes of this procedure, all references are to release 8.5, but you can substitute 8.5.5 where applicable.

To install an IBM WebSphere Application Server 8.5:

Start the IBM Installation Manager, which you must have previously installed as described in the preceding chapter of this guide entitled: Section 3.2, 'Installing the IBM Installation Manager'.
To start the Installation Manager manually, execute IBMIM from <IM_HOME>/eclipse folder. For example:
/u01/WebSphere85/InstallationManager/eclipse
The IBM Installation Manager screen displays.
You must configure the software repository in the Installation Manager before you can start the product installation. On the initial screen of the IBM Installation Manager, navigate File > Preferences.
On Preferences, click on the Add Repository... button and enter the location of the repository.config for each of the product. For example:
/u01/software/was85/nd/repository.config
/u01/software/was85/suppl/repository.config
/u01/software/was85/java17/repository.config
Optionally, if needed for your installation, you should enable a proxy server and enter proxy information.
After all repositories are added, click the Install option from the Installation Manager.
IBM Installation Manager displays a list of available products, as shown in the following example:
The IBM Install Manager displays a list of available products (packages) to install.
On Install Packages, select packages, select the products you want to install such as:
- WebSphere Network Deployment
- SDK 1.7
Click the Next button.
Note:
Once the installation begins, the installer may prompt to inform you that updates are available.
If Updates are available, the installer will display a list as shown in this example:
If the IBM Install Manager displays a list of updates, it is recommended that you click the Select Recommended button to accept and install the updates.
On Install Packages, review the International Program License Agreement and click the radio button to accept the terms if you want to continue with the installation.
On Install Packages, select location for the shared resources directory, enter an appropriate location for IMShared. These files will be used by all IBM products installed through the Installation Manager (such as HTTP Server and Customization Toolbox).
For example:
/u01/WebSphere85/IMShared
Click the Next button.
On Install Packages, package group, click the radio button entitled: Create a new package group.
In the Installation Directory field, enter an appropriate location to install the IBM WebSphere Application Server 8.5 software. It does not have to be the same location as the shared location.
For example:
/u01/WebSphere85/AppServer
Click the Next button.
On Install Packages, translations, select your desired language.
Click the Next button.
On Install Packages, select features, verify that the package for Java JDK 1.7 is selected.
Caution:
Although JDK 1.6 is the default installation, you must choose to install JDK 1.7 in order to be compatible with JD Edwards EnterpriseOne.
Click the Next button.
Click the Install button.
On Install Packages, the packages are installed, click the Finish button.
To create a profile, ensure this radio button in the right pane is selected:
Profile Management Tool to create a profile.
Continue to the next section of this chapter entitled: Section 3.4, 'Creating a New Profile for WebSphere Application Server 8.5'.

3.4Creating a New Profile for WebSphere Application Server 8.5

The section describes how to create a new profile. This profile will be used later in the installation process to create a web server and configure the plugin.

Note: This document describes how to create a 'standalone' application server. For information on how to create a cell and managed node, refer to IBM's Infocenter:

You can choose to create your first profile now or after the remaining software packages have been installed. If you create your profile now, you will need to manually define the web server before configuring the plug-in later in this chapter. As an alternative, you can use the advanced profile creation option to automatically create a web server, but this must be done after all of the other software components described in this guide are installed and updated to the correct level.

This procedure assumes you are creating a new profile at this time so that you can verify your installation.

Note:

If the Profile Management wizard did not launch, you might have encountered a bug within the eclipse XWindow Client product. You might see this error:

show 'BadWindow (invalid Window parameter)'

If you see the above error, follow the suggestions in IBM doc PM56382 at the below link, and re-launch the Profile Management Tools:

http://www-01.ibm.com/support/docview.wss?uid=swg1PM56382

If you followed the last step in the preceding chapter entitled: Section 3.3, 'Installing an IBM WebSphere Application Server 8.5 or 8.5.5', the Profile Management Tool was launched.
On WebSphere Customization Toobox, Profile Management Tool, with the Profiles tab selected, click the Create button.
On Profile Management Tools, Environment Selection, highlight the Application server environment type.
Click the Next button.
On Profile Creation Options, select the Typical profile creation radio button.
Note:
Choosing Typical profile creation uses the default configuration settings. It assigns unique names to the profile, node, and host. The tool also assigns unique port values.
Alternatively, you can choose Advanced profile creation to specify your own values for settings such as the location of the profile and names of the profile, node, and host.
Click the Next button.
On Administrative Security, clear the Enable administrative security checkbox.
Click the Next button.
On Profile Creation Summary, review the information for accuracy and click the Create button.

The progress screen is displayed. Wait for the progress to complete 100%, which may take several minutes.
Optionally, on Profile Creation Complete, you can select the check box for Launch the First steps console.
Click the Finish button.
If you chose to run First Steps, on WebSphere Application Server, First steps, select the first option, which is entitled: Installation verification.
Verify that the installation verification completed successfully. You should get the message entitled: The installation verification is complete.
Close the screen for the First steps output.
Verify that you can sign on to the Administration Console. For example:
http://host:9060/ibm/console

3.5Installing the IBM HTTP Server 8.5

The IBM HTTP Server 8.5 must be installed through the IBM Installation Manager.

In order to install the IBM HTTP server, you must have the Supplemental images in the repository, as shown in the second line item in the following screen sample.

To install an IBM HTTP Server 8.5:

Start the IBM Installation Manager, which you must have previously installed as described in the preceding chapter of this guide entitled: Section 3.2, 'Installing the IBM Installation Manager'.
Click the Install option.
On Install Packages, select packages, click the checkboxes for the HTTP Server for WebSphere Application Server and the HTTP Server Version (8.5.x).
Click the Next button.
Review the International Program License Agreement and click the radio button to accept the terms if you want to continue with the installation.
Click the Next button.
On Install Packages, package group, click the radio button entitled: Create a new package group. In the Installation Directory field, enter an appropriate location to install the IBM HTTP Server 8.5 software. It does not have to be the same location as the shared location.
For example:
/u01/WebSphere85/HTTPServer
This document refers to a local IBM HTTP server installed on the same machine as the IBM WebSphere Application Server. For instructions on how to install a remote HTTP server, refer to the IBM info center:
Also note that the shared location that you defined when you installed the IBM WebSphere Application Server in the previous section cannot be changed.
Click the Next button.
On Install Packages, select the features to install, verify the package you chose is selected.
Click the Next button.
On Install Packages, configuration, complete these fields:
- HTTP Port
  Specify a port for IBM HTTP Server to communicate. The default port is 80. If the default port is already in use, then change to another port that is available. Running IBM HTTP Server without root or Administrative privilege might restrict use of ports below 1024.
Click the Next button.
On Install Packages, review summary information, verify the accuracy of the selections.
Click the Install button to begin the installation of the IBM HTTP Server.
On Install Packages, verify the installation completed successfully. You may want to click the link: View Log File.
Click the Finish button.
You are returned to the IBM Installation Manager home screen.
To install the plug-ins, continue to the next section entitled: Section 3.6, 'Installing Web Server Plug-ins for IBM WebSphere Application Server'.

3.6Installing Web Server Plug-ins for IBM WebSphere Application Server

As with the previous software packages described in this guide, the plug-ins for IBM WebSphere Application Server 8.5 must be installed using the IBM Installation Manager.

In order to install the IBM HTTP server, you must have the Supplemental images in the repository, as shown in the second line item in the following screen sample.

To install Web Server Plug-ins for IBM WebSphere Applications Server:

Start the IBM Installation Manager, which you must have previously installed as described in the preceding chapter of this guide entitled: Section 3.2, 'Installing the IBM Installation Manager'.
On IBM Installation Manager, click the Install option.
On Install Packages, select packages, click the checkboxes for the Web Server Plug-ins for WebSphere Application Server and the HTTP Server Version (8.5.x).
Click the Next button.
On Install Packages, review the International Program License Agreement and click the radio button to accept the terms if you want to continue with the installation.
Click the Next button.
On Install Packages, package group, click the radio button entitled: Create a new package group.
In the Installation Directory field, enter an appropriate location to install the Web Server Plugins for IBM WebSphere Application Server 8.5.
For example:
/u01/WebSphere85/Plugins
Verify the SDK level. At this point in the process in this guide, SDK 1.6 is still the default installation.
On Install Packages, review summary information, verify the accuracy of the selections.
Click the Install button to begin the installation of the JDK.
The progress screen is displayed. Wait for the progress to complete 100%, which may take several minutes.
On Install Packages, verify the installation completed successfully. You may want to click the link: View Log File.
Click the Finish button.
You are returned to the IBM Installation Manager home screen.
To install the plug-ins, continue to the next section entitled: Section 3.9, 'Installing the WebSphere Customization Toolbox'.

3.7 Enabling SDK 7.0 on WebSphere Application Server 8.5

Starting with WebSphere Application Server 8.5, SDK 7.0 is supported as an optional feature. The java 1.6 is still the default installation.

Caution:

JD Edwards EnterpriseOne supports WebSphere Application Server 8.5 running with SDK 7.0 only. You must switch the java level after the installation is completed.

You can switch the java level by using the managesdk command. The executable for the managesdk command is located in the bin directory of your application server. For example:

/u01/WebSphere85/AppServer/bin

This section discusses how to use the managesdk command for these purposes:

View Available Java Products

Use this command to view the available Java products:

managesdk.sh -listAvailable

The following shows a sample of returned information.

View Available Java Products with Detail Information

Use this command to view the available Java products with detail information:

managesdk.sh -listAvailable -verbose

The following shows sample returned information.

Syntax Examples using the managesdk Command

The following examples demonstrate correct syntax when you run the managesdk command:

3.8 Switching to SDK 7.0 on WebSphere Application Server 8.5

Caution:

JD Edwards EnterpriseOne supports WebSphere Application Server 8.5 running with SDK 7.0 only. You must switch the java level after the installation is completed.

This section describes these topics:

3.8.1 Working with the managesdk Command

This section discusses how to use the managesdk command for these purposes:

View List of Available SDK Names

Use this command to view a list of available SDK names for the product installation:

managesdk.sh -listAvailable

The following shows sample returned information.

Set the command default to the version 7.0 SDK

Use this command to set the command default to the version 7.0 SDK:

managesdk.sh -setCommandDefault -sdkname 1.7_64

The following shows sample returned information.

Set the New Profile Default to the Version 7.0 SDK

Use this command to set the new profile default to version 7.0 SDK:

managesdk.sh -setNewProfileDefault -sdkname 1.7_64

The following shows sample returned information.

If Profiles Already Exist, Enable the Profiles to use the Version 7.0 SDK

If profiles already exist, use this command to enable the profiles to use the version 7.0 SDK:

managesdk.sh -enableProfileAll -sdkname 1.7_64 -enableServers

The following shows sample returned information.

Note:

To change federated profiles in a Network Deployment installation, the deployment manager must be running. The managesdk command updates the master configuration repository. After the command runs, a synchronization operation must occur before the new SDK can be used for federated profiles.

3.8.2 Modify the JD Edwards EnterpriseOne Server Manager Agent with JRE 1.7.0

Use this procedure to modify the Server Manager Agent with JRE 1.7.0:

Stop the JD Edwards EnterpriseOne Server Manager Agent.
Copy the JRE folder from the JDK 1.7 version to this folder:
/jde_home/SCFHA/jdk
Start the JD Edwards EnterpriseOne Server Manager Agent.

Note:

AIX Platform. You must obtain the IBM JDK for the AIX platform.

HP-UX Platform. You must obtain the HP JDK for HP-UX.

3.9Installing the WebSphere Customization Toolbox

New tool functionality with IBM WebSphere 8.5 includes the requirement to install the WebSphere Customization Toolbox. This tool aids in configuring your plug-in properly. The WebSphere Customization Toolbox comes from the supplemental software repository that was downloaded, decompressed, and added to the repository list as described in previous procedures in this document.

Start the IBM Installation Manager.
On IBM Installation Manager, click the Install option.
On Install Packages, select packages, select the two check boxes for WebSphere Customization Toolbox and his package and version Version 8.5.x.
Click the Next button.
On Install Packages, review the International Program License Agreement and click the radio button to accept the terms if you want to continue with the installation.
Click the Next button.
On Install Packages, package group, click the radio button entitled: Create a new package group.
In the Installation Directory field, enter an appropriate location to install the WebSphere Customization Toolbox 8.5.
For example:
/u01/WebSphere85/Toolbox/WCT/wct.sh
Click the Next button.
On Install Packages, select features, select Web Server Plug-ins Configuration Tool.
Click the Next button.
On Install Packages, review summary information, verify the accuracy of the selections.
Click the Install button to begin the installation of the WebSphere Customization Toolbox.

The progress screen is displayed. Wait for the progress to complete 100%, which may take several minutes.
On Install Packages, verify the installation completed successfully. You may want to click the link: View Log File.
Click the Finish button.
You are returned to the IBM Installation Manager home screen.

3.10Installing or Updating to WebSphere 8.5 Fix Pack

Use these procedures to install or update your existing WebSphere components to WebSphere 8.5.0 Fix Pack:

3.10.1 Updating the IBM Installation Manager to WebSphere 8.5 or Greater

Use this procedure to update the IBM Installation Manager.

Note:

For instructions on installing the Update Installer itself, refer to the section of this guide entitled: Section 4.4, 'Installing the WebSphere Update Installer'.

Start the IBM Installation Manager using the IBMIM executable..
Open the Preferences of the IBM Installation Manager.
Highlight the Updates node and select this checkbox:
Search for Installation Manager Updates
Log out of IBM Installation Manager.
Log in to the Installation Manager and you will be prompted if a new version of Installation Manager is available.
On IBM Installation Manager, click the Yes button and follow the installation wizard to complete the upgrade.

3.10.2 Updating WebSphere Application Server 8.5 or Greater

Use this procedure to update WebSphere 8.5 or greater.

Stop all the WebSphere Processes including the HTTP Server and Web Server.
Launch the IBM Installation Manager using the IBMIM executable.
Select the Update option.
On Package Group Name, select the IBM WebSphere Application Server product to which you wish to upgrade. For example:
IBM WebSphere Application Server V8.5
On Password Required, enter valid credentials for your IBM ID to connect to the IBM download site by completing these fields:
- User name
- Password
Note:
You can uncheck the Show Recommended only option to list all available fix packs.
Review the license agreement and accept the terms in order to continue.
You can accept the recommended fix packs that are automatically checked.
Note:
The recommended fix packs may vary depends on the platform.
On Features, use the checkboxes to select the components you want to install.
On Features to Install, review the summary of components that you have selected and click the Update button.

The update process downloads the fix pack from the IBM web site. The download speed depends on the network connections.
Click the Finish button when the update is completed as indicated by this message:
The packages are updated.

3.10.3 Working with the HTTP Server Component

Use this procedure to install or update the IBM HTTP Server Component for WebSphere 8.5 or greater.

Launch the IBM Installation Manager using the IBMIM executable.
Select the Update option.
On Update, select this component for the version you want to install or update:
IBM HTTP Server
On Features to Install, review the summary of selected features and click Update.
Click the Finish button when the update is completed as indicated by this message:
The packages are updated.

3.10.4 Working with the Plug-ins Component

Use this procedure to install or update the Plug-ins Component for WebSphere 8.5 or greater.

Launch the IBM Installation Manager using the IBMIM executable.
Select the Update option.
On Update, select this component for the version you want to install or update:
Web Server Plug-ins for IBM WebSphere Application Server
On Features, review the summary of selected features and click Update.
Click the Finish button when the update is completed as indicated by this message:
The packages are updated.

3.10.5 Working with the Customization Toolbox Component

Use this procedure to install or update the Customization Toolbox Component to WebSphere 8.5 or greater.

Launch the IBM Installation Manager using the IBMIM executable.
Select the Update option.
On Update, select this component for the version you want to install or update:
WebSphere Customization Toolbox
On Features, verify the component you want to installed is selected..
On Update, review the summary of selected features and click Update.
Click the Finish button when the update is completed as indicated by this message:
The packages are updated.
Restart all HTTP Services.
Restart all Web Server instances.

3.11Configuring the IBM Web Server Plug-in

After you have updated all software packages as described in the preceding section of this document entitled: Section 3.10, 'Installing or Updating to WebSphere 8.5 Fix Pack', you must configure the plug-in. This process is performed through the IBM WebSphere Customization Toolbox. You must complete this configuration before you install the JD Edwards EnterpriseOne HTML Web Server.

Start the WebSphere Customization Toolbox by starting the executable in this directory:
/u01/WebSphere85/Toolbox/WCT/wct.sh
On WebSphere Customization Toolbox, Welcome, in the list of provided tools, highlight the Web Server Plug-ins Configuration Tool.
Click the Launch Selected Tool button.
In the Web Server Plug-in Runtime Location section, click the Add button.
On Add Web Server Plug-in Location, complete these fields:
- Name
  Enter a name for the plug-in location. For example:
  IHS_webserver1
- Location
  Enter the location of your plug-in. The default plug-in directory is:
  /u01/WebSphere85/Plugins
Click the Finish button.
In the upper half of the form (shown above), verify the plug-in location that you just defined is displayed in the Web Server Plug-in Runtime Locations section in the upper half of the form.
In the lower half of the screen (shown above), click the Create button.
On Web Server Selection, choose this radio button:
IBM HTTP Server V8.5.
On Web Server Architecture Selection, choose your bitness.
On Web Server Configuration File Selection, complete these fields:
- Select the existing IBM HTTP Server httpd.conf file
  Enter in the location of your httpd.conf file. For example:
  /u01/WebSphere85/HTTPServer/conf/httpd.conf
- Specify the Web server port
  Specify a web server port that matches the port used by your HTTP server.
Click the Next button.

You will receive the Non-Administrative user configuration limitation screen if you are not logged on as an administrative user.
Click the Next button.
If you are signed on as an Administrative User, you will see the above screen. You can choose to create a user ID for IBM HTTP Server.
Click the Next button.
You can choose whether to use a Windows service to run IBM HTTP Server administration server. It is recommended that you select to run the Server as a Windows Service. Optionally you can change the startup type to Manual if you are not going to use the HTTP Administration server often.
On Web Server Definition name, specify a web server name. If you already have a web server defined (for example, webserver1), then you should use the same name here.

For the purposes of this guide, it is assumed that the HTTP Server and WebSphere Application Server are located on the same machine. Therefore, on Configuration Scenario Selection, the radio button for (Local) Installation location of WebSphere Application Server is selected.
Use the Browse button to locate the installation location of the WebSphere Application Server. For example:
/u01/WebSphere85/AppServer
Click the Next button.
On WebSphere Application Server Profile Selection, use the drop-down menu in Available Profiles to select the WebSphere Application Server profile to configure with the current Web server plug-in and create the Web server definition. For example, an available profile might be named AppSvr01.
Note: If the Available Profiles field is blank and no options show on the drop down, you must Cancel from this procedure. Create a profile and either use the advanced option to automatically create a web server definition or manually create the web server in the IBM WebSphere Application Server Administrative Console. For more information on either option, refer to the IBM info center:
http://www-01.ibm.com/software/webservers/appserv/was/library/
Click the Next button.
On Plug-in Configuration Summary, review the information for accuracy.
Click the Configure > button.
On Plug-in Configuration Result, verify that the configuration completed successfully. If necessary, follow the instructions to correct any errors.
Click the Finish button.
On WebSphere Customization Toolbox, with the Web Server Plug-in Configurations tab selected, verify that the server definition exists.

3.12Setting the HTTP Server Properties

To use IBM WebSphere Application Server 8.5 properly with Oracle JD Edwards EnterpriseOne, you must set the HTTP server to automatically generate and propagate the plug-in. These steps briefly describe this process.

Log into the admin console for IBM WebSphere Application Server
Select Servers > Server Types > Web Servers.
Select your web server.
On the right hand side of the screen, select Additional Properties > Plug-in properties.
Make any necessary changes and ensure the checkboxes are selected next to these two properties:
- Automatically generate the plug-in configuration file
- Automatically propagate plug-in configuration file
Click Apply.
Click the Save button to save all changes.

3.13Manually Generating a Plug-in

Occasionally, you may to manually generate the web server plug-in. The most common error that requires manual plug-in generation is the 'HTTP 404' when trying to access the software. This section briefly explains how to manually generate the plug-in.

Log in to the WebSphere Application Server Administration Console for your profile.
Select Server Types > Web Servers.
Check the box next to the web server definition.
Click the Generate Plug-in button.
Click the Propagate Plug-in button.
Log off of the Admin Console.

Note:

Federated (Clustered) Web Servers. If you are using WebSphere Application Server and running JD Edwards EnterpriseOne as part of a federated (or clustered) web server, you may need to regenerate the WebSphere global plugin configuration after deploying the newest tools release. This is required when new servlets have been added to the tools release you are deploying.

To update (regenerate) plugins, refer to the following procedure.

To update (regenerate) and propagate the global web server plugin configuration:

Log on to the Deployment Manager Administration Console using the Dmgr01 profile.
Expand the Environment node and select Update global Web server plug-in configuration.
Review the content in the right-hand pane and note the location of the plug-in file in the description. For example, the description might say:
The global plugin-cfg.xml file is placed in the %was_profile_home%/config/cells directory.
Click the OK button.

3.14 Manually Editing the HTTP Configuration File

Caution:

You must perform this step in order for JD Edwards EnterpriseOne HTML Server to work correctly.

To manually edit the HTTP configuration file (httpd.conf):

Locate your httpd.conf file. Typically the file is located in this directory:
/u01/WebSphere85/HTTPServer/config
Open the file with an ASCII editor.
Assuming the location of your httpd.conf is that shown in the previous step, add the following lines to the bottom of the file:
LoadModule was_ap22_module '/u01/WebSphere85/Plugins/bin/64bits/mod_was_ap22_http.so'
Note:
The extension of the mod_was_ap22_http file varies based on platform.
WebSpherePluginConfig '/u01/WebSphere85/Plugins/config/webserver1/plugin-cfg.xml'
Save and close the httpd.conf file.
Stop the HTTP Server from the bin directory using this command:
./apachectl stop
Restart the HTTP Server from the bin directory using this command:
./apachectl start

-->

by Robert McMurray

Introduction to the Windows Web Platform

The Microsoft Web Platform gives you the framework, web server, database and tools your customers need to build and run Web sites and applications on Windows. It provides a complete ecosystem of products, technologies, partners, and customers. You will be able to easily setup your servers with <link:WebPI>, test your environment using the same experience your users will have with <link:WebMatrix>, promote your offerings through the <link: Hosting Gallery>, and have quick access to the latest platform updates. The following sections will guide you through the process of configuring your servers using all the elements of the platform.

Tools	Customer	Web Hosting Provider
Web Platform Installer (Web PI)	Installs Web Platform Tools and Apps	Installs Web Plat Tools and Apps
WebMatrix	Installs/Develops Applications, Customizes, and Publishes to Hosting Provider	Supports customers publishing through WebMatrix by configuring <link:Web Deploy>
Web Hosting Gallery	Browse/Search for hosting	Publishes offerings
Web Application Gallery	Browse/Search for Web Applications to customize and publish to a hosting provider	Supports these popular applications
WebsitePanel	Uses it to manage their Hosting Account and resources	Uses it to manage their plans, customers, resource allocation, and provisioning

Image 4: The Microsoft Web Platform Ecosystem

Gopanel 1 9 2 – Manage Web Servers 1 8 Bit

Configure your Hyper-v Host for Shared Web Hosting

As we discussed earlier, you can setup a shared hosting environment with a basic configuration consisting of a single server. The following steps will guide you through the setup of a single server running as a Hyper-v host. This server will host the three VM Servers as described above.

To get started, setup the hyper-v host server with Windows Server 2008 R2 Enterprise. This version of Windows includes four guest licenses (Windows Server Standard or Enterprise); it allows you to setup the host with four guests and pay monthly only for the host server after you have customer websites in any of the guest servers.

a. Click the 'Server Manager' button in the task bar; or click 'Start' menu, type 'Server Manager' and press Enter. This will bring up the Server Manager application.

b. On the left panel of Server Manager click on 'Roles'

c. Under 'Roles Summary' click on 'Add Roles'. Follow the Add Roles Wizard to Add the Hyper-v role. The wizard will ask you to reboot the computer; when you log back in, the wizard will complete the Hyper-v configuration.

Create your Web Server VM

This section will guide you through the creation of a guest VM to be the Web Server using Windows Server 2008 R2 SP1 Standard.

a. On the host machine, click the 'Start' menu, type 'Hyper-v Manager' and press Enter. This will bring up the Hyper-v Manager application.

b. On the 'Actions' bar (right side) click 'New' and select 'Virtual Machine'. The New virtual Machine Wizard will come up.

c. Enter the name of the virtual machine, I usually use a descriptive name that refers to the OS version used, for example 'WS2K8R2Std'.

d. On the same screen, select the location of where in disk the virtual machine will be stored. Do so by checking the check box and selecting the location you will use for the Web Server VM.

e. If you already have a prepared virtual hard disk available, this is the moment to specify to use it for your VM; otherwise you could create one from scratch or attach one later.

f. The next step is to install the OS, you have several options, for some of them you need to have the OS media ready. If you have not visited the SPLA site to download Windows Server 2008 R2 SP1 Standard, now is the time. You can use the downloaded OS in this step or do it later from a DVD, network drive, or network-based installation server.

From this point on your VM will be ready for you to start and connect to, use the Hyper-v Manager and double click on the machine listed under 'Virtual Machines' in the center panel.

Gopanel 1 9 2 – Manage Web Servers 1 8 Free

Configure the Web Server Components to support WebMatrix

This article will walk you through installing the required server components to be WebMatrix compatible and fulfill the Spotlight requirements for the Web Hosting Gallery.

To simplify the installation of the web server components, we highly recommend installing Web Platform Installer, also known as WebPI, on both machines. WebPI is a tool that automates the installation of a vast majority of server components and other products for Microsoft's Web Platform.

Get WebPI 3.0 here: https://go.microsoft.com/fwlink/?LinkID=194638

If you prefer to not use WebPI, all of the required components can also be installed by hand or via your own provisioning scripts.

Option 1: Via Web Platform Installer 3.0 (recommended)

If you have WebPI 3.0 installed, the following link will automatically launch it with all of the basic web server components you'll need ready to install:

Login in the VM created in the previous section, use your administration account. Notice that these instructions will work regardless of whether you are using a VM or an actual machine.
Install Spotlight Components using Web PI. This link will install WebPI (if you have not done so already) and will let you review the list of products and dependencies before you start the process of installing the components. Notice that this list of components completely fulfills the Spotlight requirements from the Web Hosting Gallery.
Once the Web PI window is displayed, click the 'Items to be installed' link to review the list of products and dependencies.
Scroll down to see the rest of the items in the list:
Here is the list of Products to install:
1. IIS 7 or above Web Server including the following modules: Web Deploy 2.0, FTP, Media Services 3.0, IIS Remote Management Services, CGI, URL Rewrite 2.0, SQL Server 2008 Management Objects (SMO), Windows Cache 1.1 for PHP, MySQL Connector, Microsoft SQL Server Driver for PHP 2.0
2. Frameworks: .NET 3.5 SP1, .NET 4.0, ASP.NET, ASP.NET MVC, and PHP 5.2.14 or higher
Review the license page and accept the terms to continue with the install:
If you are not using Windows Server 2008 R2 SP1, install the following Web Server Patch: Extensionless URL Hotfix. This hotfix is required for ASP.NET Web Pages to function correctly. It is discussed further in this blog post.
(Optional) Install Spotlight Components plus PHP/MySQL related components using Web PI. Many of the web applications that can be published by WebMatrix have PHP/MySQL components as requirements. To ensure you are able to support those applications, you can use this link to install everything above plus PHP/MySQL related components

Option 2: Manually install Web Server components

Here is the full list of which components are installed by those links, so you can confirm against the list of products listed in WebPI. Note that many of them bring in dependencies – that is expected behavior – but the total download should not exceed 50 MB or so.

Server:

[Required] IIS 7 Web Server basic components. Required for basic web server functionality.

Frameworks:

[Required] .NET Framework 3.5 SP1. Some applications depend on this framework
[Required] .NET Framework 4.0. Some applications depend on this framework
[Optional] PHP (5.2.14 or higher). This is not required for Spotlight, but many applications that can be published by WebMatrix depend on this framework

ASP.NET:

[Required] ASP.NET. This framework is the backend of many of the most popular web applications
[Required] ASP.NET MVC 1.0. A handful of applications in the App Gallery depend on this installed centrally
[Optional] You can also optionally install ASP.NET MVC3 and ASP.NET Web Pages, which gives you the ability to host applications written in the new 'Razor' syntax of ASP.NET. However, note that the binaries required for these kinds of applications are automatically published by WebMatrix. That is, each end user who publishes applications of this type will automatically end up with the required binaries in a /bin/ folder within their site root directory, so it is not really necessary to install them centrally.

IIS Modules:

[Required] Microsoft Web Deploy. Web Deploy is a client-server tool that simplifies the deployment of sites and applications to IIS servers. While WebMatrix supports web application publishing using both FTP and Web Deploy protocols, the latter providers a faster, more secure, and richer experience. It also lets the user deploy whole apps, including databases, ensuring they work both locally and remotely. It is the highlight of the WebMatrix publishing story.
[Required] FTP Publishing Service. To ensure the option of FTP exists for maximum compatibility
[Optional] Media Services. For IIS Smooth Streaming support
[Required] IIS Remote Management Service. To allow your users to manage aspects of their accounts using the IIS console. Also a dependency for Web Deploy to function properly
[Required] FastCGI for IIS. Provides a much faster CGI implementation than the default
[Required] URL Rewrite. A dependency for many applications to function correctly
[Required] SQL Server 2008 Management Objects. A dependency for many applications to function correctly, and for WebDeploy to manage SQL Server db's.
[Optional] Windows Cache Extension 1.1 for PHP. Highly recommended when running PHP on Windows.
[Optional] MySQL Connector/Net 6.2.3 or higher. Necessary for .NET applications using MySQL databases
[Optional] Microsoft Drivers for PHP for SQL Server in IIS. Necessary for PHP applications using SQL Server
Extensionless URL Hotfix. Needed only if you are not using Windows 2008 R2 SP1. Required for ASP.NET Web Pages to function correctly. It is discussed further in this blog post.

Database Server Components (see next section):

[Optional] PHP Driver for SQL Server. We highly recommended installing this component on your database server if you are supporting PHP.

Next Steps:

• Proceed to configure the database server machine.

• Ensure that the Web Deploy 2.0 (or higher) component is configured to allow delegated deployments. This is critical, as it is the primary method that allows your customers to publish to your servers with WebMatrix.

Create & Configure your SQL Server VM

Create a second guest as the Database Server Virtual Machine

Follow the same steps outlined in 'Create your Web Server VM' to create the Database Server VM.
Add Database Server Components to the Database VM
1. Download the SQL Server 2008 R2 Web media from the SPLA site, find the link in the email you received confirming your SPLA agreement.
2. [Required] Install SQL Server 2008 R2 Web on the Database VM. Follow the installation wizard instructions. WebPI supports installing Microsoft SQL Server 2008 Express edition, but we do not recommend this product in shared hosting environments, you should use the full version instead on a separate server.
3. Install MySQL, use the following related article to ensure the installation supports WebMatrix.

Configure your Content Server VM

Create a third guest as the Content Server Virtual Machine

Download the Windows Server 2008 R2 Enterprise media from the SPLA site, find the link in the email you received confirming your SPLA agreement.
Follow the same steps outlined in 2.a to create the VM Server.
Install the Windows Server Backup features in the content server:
1. Click the 'Server Manager' button in the task bar; or click 'Start' menu, type 'Server Manager' and press Enter. This will run the Server Manager application.
2. On the left panel of Server Manager click on 'Features'
3. Under 'Features Summary' click on 'Add Features'. Follow the Add Features Wizard to Add the Backup service.
Install the File Services role in the content server.
1. Click the 'Server Manager' button in the task bar; or click the 'Start' menu, type 'Server Manager' and press Enter. This will run the Server Manager application.
2. On the left panel of Server Manager click on 'Roles'
3. Under 'Roles Summary' click on 'Add Roles'. Follow the Add Roles Wizard to Add the 'File Services' role.

Configure your Control Panel Server VM

Create a second Web Server VM, configure follow the same steps that you did for the first Web Server. This server will act as the Control Panel server; it will host WebsitePanel (we will install it in a subsequent section). It could also help you troubleshoot websites issues. This final VM will complete the four guests allowed by your Windows Server Enterprise 2008 R2 license. If you are planning on a larger deployment, you may want to use the Windows Server 2008 R2 Datacenter edition which has no license limits on guests.