Excerpt for IBM WEBSPHERE Frequently Asked Questions by Equity Press , available in its entirety at Smashwords

IBM WEBSPHERE

Frequently Asked Questions



By Equity Press



Compiled and Edited by Terry Sanchez-Clark



IBM WEBSPHERE Frequently Asked Questions



ISBN: 978-1-60332-008-5



Smashwords Edition



Edited By: Jamie Fisher



Copyright© 2007 Equity Press and IBM COOKBOOK all rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) without either the prior written permission of the publisher or a license permitting restricted copying in the United States or abroad.



The scanning, uploading and distribution of this book via the internet or via any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions, and do not participate in or encourage piracy of copyrighted materials.



The programs in this book have been included for

instructional value only. They have been tested with

care but are not guaranteed for any particular purpose.

The publisher does not offer any warranties or

representations nor does it accept any liabilities with

respect to the programs.



Trademarks: All trademarks are the property of their respective owners. Equity Press is not associated with any product or vendor mentioned in this book.



Please visit our website at www.ibmcookbook.com



Table of Contents



Introduction



Question 1: WebSphere Business Integration Modeler Entry Edition v5.1 and WebSphere Business Integration Modeler Advanced Edition V5.1

Question 2: Importing Microsoft Visio files into WebSphere

Question 3: Export formats

Question 4: Admin Console Access

Question 5: Websphere V5.0 Security Issue

Question 6: WebSphere + Tivoli Directory Server: Web Admin Tool problems

Question 7: Out of memory problem

Question 8: Cloning Websphere configuration

Question 9: Configuring plugin-cfg.xml for Load balancing in WAS5.1.1.10

Question 10: Virtual Host/WebGroup Not Found

Question 11: Migrating from tomcat to WAS

Question 12: WAS IBMIHS and Virtual Hosts

Question 13: Error creating "SOAP" connection to host "localhost"

Question 14: WAS 5.1.1 with jre 1.4

Question 15: Version of Websphere running

Question 16: Changing context root via the WAS console

Question 17: Running JUNIT code against a standalone service

Question 18: Updating web server plug-in

Question 19: Wsadmin/jacl script

Question 20: Resource Analyzer

Question 21: com.ibm.rmi.iiop.WorkerThread problem

Question 22: session.getAttribute only works with local host URL

Question 23: Websphere studio application developer

Question 24: DirectTalk voice response

Question 25: WSAD Debug server mode will not compile JSPs

Question 26: Error 503: Failed to load target servlet [portal]

Question 27: Websphere installation

Question 28: Debug Mode - Disable Step by Step

Question 29: Newbie with wrong Eclipse setting

Question 30: Detailed instructional material for websphere

Question 31: Automating installation

Question 32: JavaBean -> PCML -> RPG

Question 33: Installing DeploymentManager Server without an appserver server1

Question 34: PCML Exception

Question 35: Websphere application server help

Question 36: Wsadmin - JVM custom properties

Question 37: StaleConnection exception on WAS 4.x

Question 38: WebSphere administrator

Question 39: WebSphere Error: Failed Initialization

Question 40: WebSphere global security breaks admin console

Question 41: IBM WS AdminServer 4.0 service terminated with service-specific error

Question 42: IBM Websphere & IIS

Question 43: Installing mqseries 5.3 on windows XP

Question 44: Learning websphere

Question 45: Plug-in development in WebSphere

Question 46: Websphere 4 XMLConfig import problems

Question 47: IBM HTTP Server talking to a WebSphere machine on AIX

Question 48: Getting the list of channels

Question 49: Publishing web services problem

Question 50: Problem in installation on AIX and Solaris

Question 51: WAS 5.0 does not recompile JSP files

Question 52: encountering WorkRolledbackException

Question 53: SSL Configuration Problem

Question 54: WebSphere 5 Embedded Messaging

Question 55: Two versions of WAS on the same machine

Question 56: Deployment Files in Websphere App developer

Question 57: IBM wsdk v5 running appserver command errors

Question 58: Websphere Server Set-up

Question 59: Too many open files

Question 60: WAS50 JMS IllegalStateException calling setMessageListener

Question 61: Websphere Application Server Express V5 for iSeries

Question 62: Data source Problem WS 5

Question 63: Deploying JSP and Javabeans on WAS4.0

Question 64: Deploying application using scripting and specify classpath

Question 65: Running Admin as non root (AIX) in WAS 5

Question 66: servlet 2.3 api in Websphere 4

Question 67: IBM HTTP Server ssl configuration problem

Question 68: IBM HTTP server at windows 2000 startup

Question 69: websphere and the command line

Question 70: IBM WS Admin server doesn’t start

Question 71: Installation of WebSphere 5

Question 72: tag lib with websphere 3.5

Question 73: Application Client machine setup and deployment

Question 74: Oracle Data Source Driver

Question 75: Connection to AS400

Question 76: WAS 4.0 and ConnPool

Question 77: Silent install

Question 78: Keeping WAS 4.0 from serving up html pages

Question 79: Installing websphere and displaying wrong code

Question 80: Exception error

Question 81: Creating Virtual Host in WebSphere Application Server

Question 82: Setting KEEPGENERATED using Websphere console

Question 83: GIOPVersionException

Question 84: Duplicate another server including WAS applications

Question 85: Scheduling a task in Websphere

Question 86: The difference between direct jdbc connections and data sources

Question 87: Role of Websphere

Question 88: Convert to a WAR file

Question 89: Setting up a cluster

Question 90: Websphere 4.0 installation and install shield error

Question 91: Using a CMP MS Access database on Win2000 & WAS 4.0

Question 92: Websphere and XML message

Question 93: WebSphere MQ and server connection

Question 94: Return code 2033 on a Solaris server

Question 95: Finding the directory entry for a created queue manager

Question 96: Error message “MSGSo2ooE: the broker DataFlowEngine return code was: 1”

Question 97: Asynchronous message listener and asynchronous queue receiver

Question 98: AMQ6119 an internal MQSeries error

Question 99: Error AMQ7077 – not authorized to run the command

Question 100: Error 2035 when using COD report

Question 101: Two queue manager names on the same network



References



Introduction



WebSphere refers to a brand of IBM software products, although the term also popularly refers to one specific product: WebSphere Application Server (WAS). WebSphere helped define the middleware software category and is designed to set up, operate and integrate e-business applications across multiple computing platforms using Web technologies. It includes both the run-time components (like WAS) and the tools to develop applications that will run on WAS.



The WebSphere Business Integration Server offers to facilitate the following business needs:



1. Process Automation - Coordinates business process activities that span multiple applications, which may be geographically local or remote, internal or external to an organization.

2. Process and Workforce Management - Coordinates long-lived activities that span multiple systems and workforce groups. Avoid bottlenecks by automating and managing task list assignment, rather than specific emails to individuals.

3. Application Integration - Coordinates information flows by transformation, distribution and enrichment of in-flight messages across the enterprise.

4. Application Connectivity - Connect applications, technologies, industry standards, data sources, and mainframes within and outside the enterprise.

5. Integrated Visual Tooling - Manage, design, test, and deploy business process solutions in a team development environment.



With WebSphere Business Integration Modeler V5.1, you can complete the following key modeling activities:



1. Graphically model your current and potential business processes

2. View your models as 'swimlanes' to see how each resource you use relates to the activities in your model

3. Perform simulations to see how your processes will perform under different "what if" scenarios and environmental conditions

4. Analyze the simulation results to determine how to correct problem areas in your models, such as bottlenecks and workload imbalances

5. Generate reports from your models or simulation results using a wide variety of predefined report templates, or create your own custom reports

6. Create and update models with other team members using the team support and versioning capabilities of Business Integration Modeler

7. Print your models or reports to communicate and share the information within your organization

8. Publish models to the Web for information sharing purposes

9. Import Microsoft® Visio data as the basis or starting point for your model development

10. Jump-start your application development process by exporting your completed models to BPEL, WSDL, and XSD format, and then importing them into IBM WebSphere Studio Application Developer, Integration Edition for Linux and Windows® V5.1

11. Create workflow automation solutions from your models by exporting your completed models to FDL format, and then importing them into IBM WebSphere MQ Workflow Buildtime V3.5

12. Export your models to IBM Rational XDE for further refinement



But WebSphere Business Integration Modeler V5.1 is more than just a graphical modeling tool. It provides powerful simulation and analysis capabilities, which enable businesses to observe how their current processes perform and how they will respond to a variety of "what if" conditions, and then analyze the results to pinpoint weaknesses, such as bottlenecks to help reduce costs and generate more profit.



For businesses that are looking to move their models into the implementation phase, WebSphere Business Integration Modeler provides the exporting capabilities to transform finished models into the technology required for their business solutions, including BPEL, WSDL, and XSD for developing WebSphere Business Integration Server Foundation applications from the models, FDL for developing workflow automation solutions, or UML for further refining the models in IBM Rational XDE.



Business Integration Modeler provides three different user profiles to meet the modeling needs of a wide variety of users. Each profile exposes a different level of modeling detail to suit different modeling needs.



1. The Basic Business Modeling profile is intended for the business analyst or other user who wants to work at the high-level view of a business process model. This profile focuses on creating and displaying sequence flows and does not expose low-level technical details of process and data modeling.

2. The Intermediate Business Modeling profile gives the more technically focused user the opportunity to specify and view additional details of process and data models. For example, with this profile you can specify business rules and logic that apply to model elements and a broader set of specifications for data attributes.

3. The Advanced Business Modeling profile provides the most comprehensive level of detail for process models and data models. This profile facilitates the work of technically experienced personnel who prepare models that will be used as the basis for software applications. For example, you can use this profile to specify invocation characteristics, static fields, instance correlations, and a larger set of simulation parameters.



WebSphere Business Integration Modeler Advanced Edition V5.1 likewise offers three different technology modes so that you can develop the models in the run-time environment in which you will later deploy them. Each technology mode exposes only the functionality permitted in that run-time environment.



1. The BPEL technology mode is optimized for exporting models to Business Process Execution Language (BPEL) format, which you can then import into WebSphere Studio Application Developer Integration Edition, where you can further define the process for deploying to IBM WebSphere Business Integration Server Foundation V5.1.

2. The MQ Workflow FDL technology mode is optimized for exporting models to Flow Definition Language (FDL) format, which you can then use in WebSphere MQ Workflow V3.5 as the basis of an automated workflow solution.

3. The Operational technology mode provides the most comprehensive detail of the three technology modes. This technology mode is ideal for developing business models that are not targeted for deployment to the above runtime environments.



WebSphere Business Integration Modeler V5.1 is built using the Eclipse open source technology, allowing it to integrate and inter-operate with other Eclipse-based IBM tools, such as IBM WebSphere Studio Application Developer, Integration Edition for Linux and Windows, Version 5.1 on Windows.



With what types of files can you import into WebSphere Business Integration Modeler 5.1?



You can successfully import the following types of files:



1. FDL files (files developed in WebSphere MQ Workflow Buildtime 3.5)

2. ADF files (WebSphere Business Integration Workbench 4.2.4 models)

3. Delimited text files (to import data from other programs, such as spreadsheets or databases)

4. XSD files (XML Schema Definition)

5. VDX files (Visio files created in Microsoft Visio 2002 or 2003)

6. Business Integration Modeler V5 Projects (files created in Business Integration Modeler V5.1)



Question 1: WebSphere Business Integration Modeler Entry Edition v5.1 and WebSphere Business Integration Modeler Advanced Edition V5.1



What is the difference between WebSphere Business Integration Modeler Entry Edition V5.1 and WebSphere Business Integration Modeler Advanced Edition V5.1?



A: WebSphere Business Integration Entry Edition Version 5.1 is a low cost option for business users who are looking for a simple and easy-to-use tool to model, document, and print their business processes.



WebSphere Business Integration Advanced Edition Version 5.1 provides all the capabilities of the Entry Edition. In addition, it enables business users to perform complex simulations on their process models based on "what if" scenarios and then analyze and generate reports from the simulation results to identify problem areas in the processes, such as bottlenecks. The Advanced Edition also provides a "jump-start" to application development by enabling more technically focused users, such as IT architects, to export the models to BPEL, UML, or FDL models, for further refinement.



The following table summarizes the key functional differences between the Entry and Advanced Editions:





Question 2: Importing Microsoft Visio files into WebSphere



Can one import Microsoft Visio files into WebSphere Business Integration Modeler 5.1?



A: Yes, you can import shapes from Microsoft Visio 2002 or 2003 files into WebSphere Business Integration Modeler V5.1. These shapes can be used to create elements such as tasks and business items in WebSphere Business Integration Modeler.



Question 3: Export formats



When I have completed my models, what formats or applications can I export them to?



A: You can export models created in WebSphere Business Integration Modeler Advanced Edition V5.1 to the following file formats:



1. BPEL, WSDL, and XSD, to import into IBM WebSphere Studio Application Developer, Integration Edition for Linux and Windows V5.1; and later deploy to WebSphere Business Integration Server Foundation V5.1

2. UML, to import into Rational® XDE™

3. FDL Business Modeling Profile, to import into IBM WebSphere MQ Workflow Buildtime V3.5

4. Delimited text format (business items only)

5. Business Integration Modeler V5 Project format, to back up or share Modeler V5 projects



Question 4: Admin Console Access



After federating a node with an application server into the Deployment manager, I am unable to access the admin console of the application server but I can access the admin console of the Deployment Manager. Is this how it is supposed to be? Does access to the admin console of the application server get blocked when you federate it with a NDM?



What is the explanation for this?



A: Yes, it does get blocked. Once you federate the base to the network deployment, the control will then be from the Network deployment. There will be a node agent installed on the Base that the DMGR in the network deployment communicate to.



Question 5: Websphere V5.0 Security Issue



I am running a WAS 5.0 base deployment on Solaris with a single application server. When I turn the Global security on, I had the problem of stopping the server. Could anyone help me how to stop the server?



A: You have to stop the server using the user and password, which you use when you enabled the global security.



Go to install_root/bin directory of the WebSphere Application Server installation or a Network Deployment installation.

Generally on uix

/opt/WebSphere/AppServer/bin /stopServer.sh server1

windows:

C:\program files\IBM\WebSphere\AppServer\bin \stopServer.bat server1



Syntax:

stopServer <server> [options]



UNIX:

stopServer.sh <server_name> -user <name_of_the_user> -password <given_password>



stopServer.sh server1 -user jones -password jones123



Windows:

stopServer.bat <server_name> -user <name_of_the_user> -password <given_password>



stopServer.bat server1 -user jones -password jones123



Question 6: WebSphere + Tivoli Directory Server: Web Admin Tool problems



I use WebSphere 6.0 and am trying to use Tivoli Directory Server 6.0 with it. Installation as well as the creation of server and database went okay. In the WebSphere's Admin Console, I added IDSWebApp to the list of applications and it starts normally. But when I try logging in to Tivoli's Web Administration Tool, in the list of available hostnames, I get only "Console Admin"; logging in with superadmin+secret works.



The problem is that the two page "change admin login" and "change admin pwd" are blank and on the "manage console servers" and "manage console properties", I get nothing but two NoSuchMethodError-Exceptions that are listed below. I tried re-installing Tivoli, deactivating WebSphere's Global Security, and installing Tivoli's Fixpack (6.0.0.9), but nothing changed.



The content of the page "Manage console servers" are as follows:



Exception #0

java.lang.NoSuchMethodError: com.ibm.psw.wcl.components.table.WTable: method



getResourceBundle(Ljava/util/Locale;)Ljava/util/ResourceBundle; not found

at com.ibm.mdr.wcl.DrTableCreator.create(DrTableCreator.java:483)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:112)

at com.ibm.mdr.DrContainerCreator.recurseChildren(DrContainerCreator.java:97)

at com.ibm.mdr.wcl.DrDatagroupCreator.create(DrDatagroupCreator.java:362)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:112)

at com.ibm.mdr.DrCreatorFactory.createStateTree(DrCreatorFactory.java:77)

at com.ibm.mdr.DrStateMgr.createStateTree(DrStateMgr.java:1003)

at com.ibm.mdr.DrStateMgr.invoke(DrStateMgr.java:2539)

at com.ibm.mdr.DrRendererManager.invoke(DrRendererManager.java:377)

at com.ibm.mdr.DrRenderer.invoke(DrRenderer.java:1240)

at com.ibm.ui.framework.UserTaskManager.invoke(UserTaskManager.java:1361)

at com.ibm.ui.framework.UserTaskManager.invoke(UserTaskManager.java:1322)

at com.ibm.ldap.IDSAdmin.ConsoleServersPanel.init(ConsoleServersPanel.java:123)

at com.ibm.webnav.servlet.WnTransactionManager.processTransaction(WnTransactionManager.java:580)

at com.ibm.webnav.servlet.WnTransactionThread.run(WnTransactionThread.java:111)



The content of the page "Manage console properties":



Exception #0

java.lang.NoSuchMethodError: com.ibm.psw.wcl.components.table.WTable: method



getResourceBundle(Ljava/util/Locale;)Ljava/util/ResourceBundle; not found

at com.ibm.mdr.wcl.DrTableCreator.create(DrTableCreator.java:483)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:112)

at com.ibm.mdr.DrContainerCreator.recurseChildren(DrContainerCreator.java:97)

at com.ibm.mdr.wcl.DrGroupCreator.create(DrGroupCreator.java:224)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:112)

at com.ibm.mdr.DrContainerCreator.recurseChildren(DrContainerCreator.java:97)

at com.ibm.mdr.wcl.DrGroupCreator.create(DrGroupCreator.java:224)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:112)

at com.ibm.mdr.wcl.DrGroupCreator.recurseSelectableChildren(DrGroupCreator.java:709)

at com.ibm.mdr.wcl.DrDatagroupCreator.create(DrDatagroupCreator.java:353)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:112)

at com.ibm.mdr.DrCreatorFactory.createStateTree(DrCreatorFactory.java:77)

at com.ibm.mdr.DrStateMgr.createStateTree(DrStateMgr.java:1003)

at com.ibm.mdr.DrStateMgr.invoke(DrStateMgr.java:2539)

at com.ibm.mdr.DrRendererManager.invoke(DrRendererManager.java:377)

at com.ibm.mdr.DrRenderer.invoke(DrRenderer.java:1240)

at com.ibm.ui.framework.UserTaskManager.invoke(UserTaskManager.java:1361)

at com.ibm.ui.framework.UserTaskManager.invoke(UserTaskManager.java:1322)

at com.ibm.ldap.IDSAdmin.ConsolePropertiesPanel.init(ConsolePropertiesPanel.java:123)

at com.ibm.webnav.servlet.WnTransactionManager.processTransaction(WnTransactionManager.java:580)

at com.ibm.webnav.servlet.WnTransactionThread.run(WnTransactionThread.java:111)



How can I resolve this problem?



A: A good workaround for your problem is that instead of forcing an installation of Tivoli Directory Server in the already installed WebSphere Application Server, use the embedded version of WAS that comes along with the TDS. It is already configured for TDS. This means that you will have your WebSphere Portal Server running using the original WAS, and on the other hand, TDS runs on top of its embedded version of WAS.



Apparently, this is a waste of system resources and a possible cause for compatibility problems (2 WAS running), but it seems the best solution because the embedded WAS does not slow down the system, loads rapidly, does not get in conflict with the other WAS and you have the possibility to administer TDS independently from WebSphere.



Furthermore, if you plan your system wisely, you should use a dedicated server machine for WebSphere and another one for TDS, and in this case you are forced to use an Application Server on every machine.



Question 7: Out of memory problem



I would like to know the steps to follow to resolve an out of memory problem on a system with Websphere running on it.



Is there some advice or suggestion I can work on?



A: For your specific problem, go and visit the following site for explanations:



http://www.bmc.com/products/documents/70/31/57031/57031.pdf#search=%22out%20of%20memory%20websphere%22



Quote from the website cited:



“Garbage Collection Duration Parameter



It displays the average amount of time (over the given discovery cycle) JVM spent cleaning up unused portions of memory. This parameter:



> Is updated every five minutes.

> Is accessed by selecting WebSphere icon -> JVM server icon -> Server Resources -> Garbage Collection Duration.

JVM is in charge of gathering and reusing free memory because the J2EE specification frees the JAVA programmer from that task. Garbage collection is the process of JVM that frees unused portions of memory and returns the portions to the heap size.



Garbage collection is good and bad:



> Good, because it gives JVM more memory for JVM heap

> Bad, because JVM tends to slow down J2EE transactions during Garbage Collection



Thus, Garbage Collection is a “balancing act.” If Garbage Collection does not happen, then JVM runs out of memory. If Garbage Collection happens too often, or takes too long, your JAVA programs slow down. The Garbage Collection Duration should start small and grow over time (since initially JVM does not have a lot of memory to free up).



If your JVM is spending more than 5% of the time in Garbage Collection, you may have a problem. In Figure 4, assuming the Garbage Collection Duration is collected every 5 minutes (300 seconds), a good warning level for this parameter would be 15 seconds.”



Figure 4: Garbage Collection Duration Parameter



Question 8: Cloning Websphere configuration



We have an environment with one ND machine and two machines running each two Application Servers (vertical and horizontal cluster). There are lots of configuration options set on either the whole cell or single Application servers.



I want to set up one machine containing the ND and two Application servers with cells that have the same configuration as the other cell but different hostname and IP. Backup and restore with backupConfig.sh will not work as far as the documentation says, since it needs to have the same IP/name on restore. I could copy the whole /opt/IBM/ directory structure to the new machine and grep/sed the name/IP to the new one, but I guess that won't work.



What would be the best way to clone the configuration of a Websphere 6 with ND? Could anyone suggest some other ideas on how to do it?



A: WAS 6 supports cloning of configuration from one server to other.



Exporting and importing profiles



WebSphere Application Server V6 provides a mechanism that allows you to export certain profiles, or server objects from a profile, to an archive. The archive can be distributed and imported to other installations. An exported archive is a zip file of the configuration directory with host-specific information removed. The recommended extension of the zip file is .car. The exported archive can be the complete configuration or a subset. Importing the archive creates the configurations defined in the archive. The target configuration of an archive export / import can be a specific server or an entire profile.



To use an archive you would:



1. Export a WebSphere configuration. This creates a zip file with the configuration.

2. Unzip the files for browsing or update for use on other systems. For example, you might need to update resource references.

3. Send the configuration to the new system. An import can work with the zip file or with the expanded format.

4. Import the archive. The import process requires that you identify the object in the configuration you want to import and the target object in the existing configuration. The target can be the same object type as the archive or its parent:

– If you import a server archive to a server configuration the configurations are merged.

– If you import a server archive to a node, the server is added to the node.



A tutorial on creating and using archives can be found in the Information Center. See ftp://ftp.software.ibm.com/software/eod/WAS_6-0/SystemManagement/Presentations/WASv6_SM_Configuration_Archives/playershell.swf



Server Archives



The following command can be used to create an archive of a server:



$AdminTask exportServer {-archive <archive_location> -nodeName <node>

-serverName <server>}



This process removes applications from the server that you specify, breaks the relationship between the server that you specify and the core group of the server, cluster, or SIBus membership. If you export a single server of a cluster, the relation to the cluster is eliminated.



To import a server archive use the following command:



$AdminTask importServer {-archive <archive_location> [-nodeInArchive <node>]

[-serverInArchive <server>][-nodeName <node>] [-serverName <server>]}



When you use the importServer command, you select a configuration object in the archive as the source and select a configuration object on the system as the target. The target object can match the source object or be its parent. If the source and target are the same, the configurations are merged.



Profile Archives



The following command can be used to create an archive of a profile:



$AdminTask exportWasprofile {-archive <archive_location>}



You can only create an archive of an unfederated profile (standalone application server).



$AdminTask importWasprofile {-archive <archive_location>}



Question 9: Configuring plugin-cfg.xml for Load balancing in WAS5.1.1.10



I am trying to do Load Balancing on two Application servers from Apache Webserver. I was partially successful by getting the round robin load balancing. However, the session that I established is not permanent, i.e., for every other click, it points me to the other application server without holding the session.



How do I set up a persistent session with load balancing?



The plugin file I am using is as follows:



cat plugin-cfg.xml



<?xml version="1.0" encoding="ISO-8859-1"?>



<Config ASDisableNagle="false" AcceptAllContent="false" AppServerPortPreference="HostHeader" ChunkedResponse="false" FIPSEnable="false" IISDisableNagle="false" IISPluginPriority="High" IgnoreDNSFailures="false" RefreshInterval="60" ResponseChunkSize="64" VHostMatchingCompat="false">

<Log LogLevel="Trace" Name="/tmp/http_plugin.log"/>

<Property Name="ESIEnable" Value="true"/>

<Property Name="ESIMaxCacheSize" Value="1024"/>

<Property Name="ESIInvalidationMonitor" Value="false"/>

<VirtualHostGroup Name="default_host">

<VirtualHost Name="*:9080"/>

<VirtualHost Name="*:80"/>

<VirtualHost Name="*:9443"/>

<VirtualHost Name="*:9081"/>

<VirtualHost Name="*:9444"/>

</VirtualHostGroup>

<ServerCluster CloneSeparatorChange="false" LoadBalance="Round Robin" Name="Testh_Cluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">

<Server ConnectTimeout="0" CloneID="F1234567" ExtendedHandshake="false" LoadBalanceWeight="2" MaxConnections="-1" Name="xxxapp123_server1" ServerIOTimeout="0" WaitForContinue="false">

<Transport Hostname="xxxapp123" Port="9080" Protocol="http"/>

<Transport Hostname="xxxapp123" Port="9443" Protocol="https">

<Property Name="keyring" Value="/opt/WebSphere/AppServer/etc/plugin-key.kdb"/>

<Property Name="stashfile" Value="/opt/WebSphere/AppServer/etc/plugin-key.sth"/>

</Transport>

</Server>

<Server ConnectTimeout="0" CloneID="F1234568" ExtendedHandshake="false" LoadBalanceWeight="2" MaxConnections="-1" Name="xxxapp161_server2" ServerIOTimeout="0" WaitForContinue="false">

<Transport Hostname="xxxapp161" Port="9081" Protocol="http"/>

<Transport Hostname="xxxxapp161" Port="9444" Protocol="https">

<Property Name="keyring" Value="/opt/WebSphere/AppServer/etc/plugin-key.kdb"/>

<Property Name="stashfile" Value="/opt/WebSphere/AppServer/etc/plugin-key.sth"/>

</Transport>

</Server>

<PrimaryServers>

<Server Name="xxxapp161_server2"/>

<Server Name="xxxapp123_server1"/>

</PrimaryServers>

</ServerCluster>

<UriGroup Name="default_host_Test_Cluster_URIs">

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/pbtwes/*"/>

</UriGroup>

<Route ServerCluster="Test_Cluster" UriGroup="default_host_Test_Cluster_URIs" VirtualHostGroup="default_host"/>

<RequestMetrics armEnabled="false" loggingEnabled="true" rmEnabled="false" traceLevel="HOPS">


Purchase this book or download sample versions for your ebook reader.
(Pages 1-19 show above.)