CR097934

Errors may be experienced using the calculate HTTPS feature in a portlet.

CR063334

Core dump creating customer profile with JIT enabled on AIX.

CR079085

JVM crashes when many clients send page requests to a portal web application as soon as the server comes up.

CR080079

RuleSetNotFoundException is thrown for domains that have no rule sets

CR080278

Error when no group is selected logging into sampleportal

CR080752

Errors in the script to start the migration viewer (viewer.sh)

CR082770

Error when no group is selected logging into sampleportal

CR087498

"java.sql.SQLException: weblogic.common.ResourceException: Access not allowed" error is seen when migrating filerealm.properties commercePool or customPool from WebLogic Portal 4.0 to WebLogic Portal 7.0, 7.0 Service Pack 1, 7.0 Service Pack 2, or 7.0 Service Pack 4.

CR090608

Data Sync of a newly created discount throws DiscountParsingException

CR095079

CreateManagedConnection Error: SQL Exception: No suitable device

CR095121

sampleportal SQLException with Sybase

CR096076

Unable to use multiple Webflow namespaces in a portlet

CR097829

The web.xml file created by the Portal Wizard is malformed, resulting in a SAXParseException.

CR098629

When a portal application is deployed as an ear file you cannot subsequently modify application-config.xml using the WebLogic Server 6.1 console.

CR101849

WebLogic Portal now supports the WebLogic Server 7.0 security framework

CR76471

Concurrent portal cache access causes java.lang.NullPointerException.

CR78752 & CR62867

Socket Muxer problem from using native IO on NT.

CR78912 & CR82903

Broken link in the Portlet Wizard.

CR79828

Baseportal webapp not fully configured for all portal services.

CR80390

Hot Deploy fails with "Unable to add module" message.

CR81677

Cannot untarget and retarget a datasource.

CR83798

Unable to edit portal in a new project in the E-Business Control Center.

CR84173

Data Sync progress bar displays less than 100% after completion.

CR85808

Unable to hot deploy a portal web app to a Platform domain.

CR45118

Server terminates with weblogic.utils.AssertionError

CR70035

WebLogic Portal Console extensions do not use the WebLogic Server Console language setting

CR73489

During Data Sync, PointBase hangs with Multi-Byte Character Set data

CR76775

Internationalization tags should detect updated resource bundle files.

CR77469

Group portal names containing Multi-Byte Character Set data are not displayed properly.

CR77971

Multi-Byte Character Set data is not properly handled by the Portal Wizard.

CR78590

Portlet names containing Multi-Byte Character Set data are not properly encoded.

CR79145

Webflow namespaces can not contain Multi-Byte Character Set data

CR79160

Portal page names can not contain Multi-Byte Character Set data.

CR79175

The <i18n:getMessage> tag does not use the default language set by the <i18n:localize> tag

CR79208

International characters in portlet names causes a problem in the icon-url for the portlet.

CR79502

Icon is not properly displayed when the portlet name contains Multi-Byte Character Set data.

CR79512

create_db fails during generation of statistics (create_stats).

CR79578

configjca echoes the incorrect driver name for Oracle.

CR80231

Cannot maximize or minimize portlets whose name contains Multi-Byte Character Set data.

CR80236

Layouts are not displayed in the Admin Tools for portal pages whose name contains Multi-Byte Character Set data.

CR80283

Cannot edit portlets for portal pages whose name contains Multi-Byte Character Set data.

CR033972

The TransposeArray ID is not recognized.

CR035481

Shopping Cart Contents are lost in a clustered environment when the user logs in for the first time.

CR035483

Session TimeOut received under a cluster environment.

CR035571

Hot Deploy doesn't work for EJBs in weblogic.class.path.

CR043378

Bulk loader throws a StackOverflowError exception.

CR044675

DBCS E-mail is distorted in the preview area of the E-Business Control Center.

CR044825

Warning messages about EJB redeployment.

CR045896

Loadsampledata stops server with a Personalization or Commerce license.

CR047033

PipelineSession request-scoped attributes do not work with HTML frames and they do not work if a client has two browsers hitting the same WebLogic Commerce Server application.

CR047334

HTML Email is not sent correctly.

CR047061

Static portlets with htm/html extensions are not displayed in portal.

CR049144

HTML files cannot be portlets in the exampleportal.

CR051123

A new event cannot be saved.

CR051324

Oracle 8.1.7/Win2K loadSampleData.bat problem.

CR052709

In the web.xml file WLCS_STATIC_ROOT parameter server value is hardcoded.

CR058376

System doesn't deal with welcome file in tools, toolSupport, etc. for Web applications.

CR058616

Behavior tracking persistence should be application-scoped.

CR058726

System does not work with WebLogic Server LDAP Realm v2.

CR058836

32K data size limitation on discounts2.xml.

CR059442

Maxing-out property set definition character limit behaves in an odd manner.

CR059581

Exception handling for sample applications does not work in cluster.

CR059781

The user is not given the opportunity to correct incorrect username/password for a given connection in Connection Settings.

CR059879

Portal exceptions will not work in a cluster.

CR060145

A copy of a portal application does not use welcome files.

CR060290

LDAP Edit Group Admins authorization causes an error.

CR060301

Display Flush Size is not applied to a server until the server is restarted.

CR060341

The portal server fails to start after LoadSampleData.bat is run with an Oracle database defined with a multi-byte character set.

CR060774

Attempting to access Personalization sample WebApp using startP13n.bat returns a 404 error.

CR060799

A database deadlock occurs when multiple users logout simultaneously on NT using Oracle 8.1.7.

CR061396

A search for subgroups returns a group not found message.

CR061496

Implementation delegate needs to be created for JdbcHelper to allow CLOB/BLOB read/write using db-specific extensions to JDBC spec.

CR062205

There is no migration for CommerceInputProcessor.getPipelineSession(req,true).

CR062217

IllegalArgumentException thrown while using new layouts in portalTools.

CR063019

The portlets directory name is case sensitive. Sample XML portlets are not displayed in Explorer.

CR063049

CLOB database inserts/updates do not work with Oracle THIN driver and Delegates.

CR063919

In JSP Administration Tools the floatable attribute is missing for the portlet.

CR064026

The stockportal login select group should not show every group with other member groups.

CR064149

There is a problem with build and start in WebLogic Commerce Server. There is a webflow error due to a null for webapp.

CR064221

CTRL-M is added to multi-line properties in non-Windows OS.

CR064429

There is a definition of SQL Server 2000 classes in the set-environment.bat file.

CR064640

The browser Back button causes problems with the webflow form tag.

CR064670

The database create_all scripts do not process triggers.

CR064777

Sybase trigger errors in TU_ENTL_RULESET, TU_RESOURCE_GROUP_ADMIN and TU_P13N_LAYOUT.

CR064817

The set-environment.sh file on Linux does not set the LD_LIBRARY_PATH correctly.

CR064821

On Solaris DB2, changing the minimizable attribute of a portlet returns an exception.

CR064897

Hot deploy of input processors breaks the Web application until it is redeployed.

CR065223

The floatable attribute is missing

CR065370

In stockportal a classcast exception is received when the Multiple Group box is selected.

CR065440

Modifying and syncing E-Business Control Center Tour1 and Tour2 causes errors with because of StartPortal's malformed XML.

CR065566

An item cannot be added to the shopping cart.

CR065781

Multi-byte characters in file names corrupts the database.

CR066776

If there is a user in more than one group a java.lang.ClassCastException occurs while logging in to stockportal.

CR067696

The E-Business Control Center can get in a state where the Explorer will not return due to an expired license.

CR067935

Syncing to a UTF-8 Oracle database prevents the portal server from starting.

CR069058

<um:createUser saveAnonymous="true"> does not work

CR071557

There is a performance problem in RDBMSRealm with the RDBMSDelegate getUser() and getGroupMembers()

CR072316

Servlet filters are throwing a "java.lang.IllegalStateException: Unable to extract ServletContext from Request."

CR073932

There is an HPUX11-Sybase 12 jConnect5.2/Segment Integration problem.

CR074480

THIN settings are not in the set-env and databaseload.properties files.

CR075135

In AIX433-DB2 7.2 Native there is a problem with creating a new user.

CR075212

The webflow:validatedForm tag needs extra parameters.

CR075335

A file path reference in resourceURL.inc is incorrect and prevents skins from displaying.

CR075601

WebflowJSPHelper produces a double question mark for redirect URLs.

CR076577

The Display Flush Size is not applied to server until server is restarted.

CR076667

Linux 7.2 - Sybase 1192 have a java.lang.OutOfMemory Exception problem.

CR076825

Users are unable to target ApplicationConfiguration from the console.

CR077354

A PersistenceException is received, when syncing the E-Business Control Center from Solaris to a server with a SQL2000 database.

CR052478

ClassCastException String to javax.management.MBeanAttributeInfo#attributeType

CR064192

scc files created by Visual Source Safe are not ignored, especially by validation.

CR079688

Deleting a portlet in the E-Business Control Center does not remove it from the portal configuration.

Problem

Deleting a portlet from your file system, outside the E-Business Control center or the explorer pane within the E-Business Control Center, does not update any open portal editor windows in the E-Business Control Center that contain the deleted portlet.

Platform

All.

Workaround

Close the portal editor window and reopen it for that portal to view the updated portal definition. It will no longer show the deleted portlet as part of the portal.

CR075598

and

CR085087

Users are required to reboot the server for Web Service Portlet Wizard changes to appear.

Problem

If you redeploy an application without rebooting the server, the portal does

not pick up any new .jar files in WEB-INF/lib directory.

Platform

All.

Workaround

Redeploy the Web application from WebLogic Server Console. This method works for all Web applications except sampleportal, which is shipped with WebLogic Portal. You must reboot the server for changes made in Portlet Wizard to appear for sampleportal.

CR076345

Portlet Wizard is unable to retrieve an operation if browse feature retrieves a WSDL file with a long directory name.

Problem

When adding a Web Service to a portlet in the portlet wizard, and browsing to a WSDL file, the operation is unretrievable if the directory is longer than 255 characters.

Platform

Windows.

Workaround

Reduce the directory name length to 255 characters or less.

CR077079

Web Services Portlet Wizard .jar file names must be unique.

Problem

If a .jar file used by a Web services portlet, created by Portlet Wizard, does not have a unique file name, an exception will occur.

Platform

All.

Workaround

Make sure all .jar file names used in a Web services portlet are unique.

CR078633

Unable to select an operation from a different Web service after WebLogic Server clientgen fails on another.

Problem

In the Web Services window of the Web Services Portlet Wizard, if users select Web services that cause WebLogic Server clientgen to fail, users can not choose another valid Web service and operation. All operations from that point forward are greyed out.

Platform

All.

Workaround

Close the Web Services Portlet Wizard and start the wizard again.

CR078658

Problems occur when a portal Web application is selected as the default Web application.

Problem

When a portal Web application is selected as the default Web application, the following problems occur:

Platform

All.

Workaround

The portal Web application must be deployed under the same DNS domain that the

portal administration application is deployed.

CR079395

If a referenced web services WSDL cannot be accessed or is unavailable for one portlet, a user cannot access the entire portal Web application.

Problem

If a portlet JSP throws exceptions, user may not be able access the entire portal Web application.

Platform

All.

Workaround

CR079919

All applications should use common cookie names across Web applications if single sign-on is desired.

Problem

The weblogic.xml files for each Web application must have a common cookie name for forwarding to work correctly across Web applications.

Platform

All.

Workaround

To use a single cookie session ID across Web applications:

Change the CookieName session parameter in each Web application weblogic.xml file to the same parameter name.

For example:

<session-param>
<param-name>CookieName</param-name>
<param-value>JSESSIONID_SAMPLEPORTAL</param-value>
</session-param>

CR080181

Hot deploy status messages from the portal wizard maybe be garbled when using a non-English system locale

Problem

When using some non-English locales (such as Japanese) with the E-Business Control Center, the messages in the "Details" window of the Hot Deployment dialog box may include random strings of garbled characters.

Platform

All.

Workaround

These messages do not affect the hot deployment, and can be ignored.

CR080771

Cannot access any web applications during hot deploy in the portal wizard

Problem

During the process of hot deploying a new Web application through the E-Business Control Center, there is a moment when the previously deployed Web applications belonging to the same domain might not be accessible. You will receive an Internal Server 500 error.

This happens because hot deployment is redeploying the entire enterprise application. As a result, modules will be inaccessible for a moment until hot deployment has finished.

Platform

All.

Workaround

Wait for hot deployment to complete and then refresh the browser for an existing Web application. The Web application will then reappear.

CR080803

Cannot consecutively hot deploy to two different domains in the portal wizard

Problem

After creating two domains with the Domain Configuration Wizard, if you hot deploy a portal Web application in the first domain and then deploy a portal Web application in the second domain, the hot deploy fails in the second domain. In addition, the information in the hot deploy log says that the hot deploy was completed successfully, which is incorrect.

Platform

All.

Workaround

Before switching to a different domain, restart the E-Business Control Center. This will avoid the problem with hot deploying Web applications in different domains.

CR080109

Cannot retry after a failed hot deploy in the portal wizard

Problem

When using the Portal Wizard in the E-Business Control Center to hot deploy a web application, if the web application fails to deploy for some reason, e.g., the server was not running, or an invalid username/password was entered, there is no way to retry the deployment. You must either restart the Portal Wizard and create a new portal, or manually deploy the new portal web application.

Platform

All.

Workaround

None.

CR082251 and CR075661

Portals fail to be listed if the description includes:&,<..>

Problem

Using special characters, such as <, >, &, #, etc., in the names of portals, portlets, and portal pages may trigger errors in the E-Business Control Center and the Portal Admin Tools.

Platform

All.

Workaround

To rename portals named with special characters, edit the .portal file using a text editor and remove the special characters. To avoid errors associated with portal pages and portlets with non-alpha characters in their names, always name portal pages and portlets using only letters, numbers, and/or the "_" (underscore) character.

CR222039

A large number of personalized portals prevents server from starting.

Problem

A datasync process occurs on WebLogic Portal server startup which sync's data from a master portal copy in the database to all personalized portals. When a large amount of personalized portals (group portals and user customized portals) exist in the database, this can be a lengthy process updating all these entries. Server startup time will increase as the number of personalized portals increase..

Platform

All.

Workaround

A new switch was added to bypass the sync that occurs on server startup:

-DpropagatePortalChanges="false"

When running datasync from EBCC, a full sync is done moving changes from the EBCC files to the master copy of the portal in the database, and to all personalized portals made from that master copy. At this point all personalized portals are up-to-date and the sync on server startup is not needed. If using this flag and you are unsure if the changes in EBCC are current, re-run the manual synchronization process.

Note: When in a clustered environment, datasync should be run with all cluster nodes active. With -DpropagatePortalChanges="false" set, this is necessary because otherwise the managed servers may not be updated with the latest datasync information.

CR044788

Requirement to have separate cookie names for the session per Web application.

Problem

The sample applications for WebLogic Portal are shipped with unique cookie names configured for each Web application in the weblogic.xml descriptor, because these sample applications do not use or require the single-user sign-on feature. In this configuration, if you are using a proxy server, you will need to modify its plug-in's settings because they are normally only aware of a single cookie.

Platform

All.

Workaround

Configure the plug-ins to do proxy by path. For example:

ppath=*/webapp1/* => set CookieName="foo"
ppath=*/webapp2/* => set CookieName="bar"

CR047792

Creating users of type wlcs_customer with missing required property values in the administration tools causes template errors at login.

Problem

When creating a user of type wlcs_customer with the WebLogic Portal Administration Tools, if you do not fill in values for all required properties, you receive errors in the template when you log in with that user.

Platform

All.

Workaround

Create users of wlcs_customer type by logging into the templates using registration rather than using the administration tools. If you prefer to use the administration tools, enter values for all required user properties (fields marked with an asterisk *).

CR054787

Users logging into the Weblogic Commerce Server app experience unexpected behavior if they are not in the "wlcs_customer" group.

Problem

The WebLogic Commerce Server sample application uses a security-constraint in WEB-INF/web.xml to specify form-based authentication for the "login" link in the WebLogic Commerce Server sample application. The security-constraint is configured to allow access only to members of the CustomerRole (wlcs_customer group).

When a valid user who is not a member of wlcs_customer group attempts to log then, they will experience successful authentication, but will not be authorized to access the protected resources in the WebLogic Commerce Server sample app. This situation should be treated as an authentication failure, but it was not prior to 7.0 SP2.

Platform

All.

Workaround

This was fixed in Service Pack 2 by adding Authentication.logout() to the form-error-page (badlogin.jsp). This change causes all authentication data to be removed from the session so that the login attempt is treated as an authentication failure.

CR060948

Administrator users deleted in user management still appear in portal tools.

Problem

Admin tables are not updated when you remove a user outside of the Portal Administration tools.

Platform

All.

Workaround

CR067641

There is a need to change the default httpsInd attribute of the webflow url creation tags.

Problem

If the httpsInd attribute of the webflow url creation tags is not specified then a default value is used. It may be desirable to specify this default value.

Platform

All.

Workaround

<context-param>
<param-name>HTTPSIND_DEFAULT_VALUE</param-name>
<!—
the desired default value. See the docs for the
weblfow url creation tags for more information on the
possible values
-->
<param-value>CALCULATE</param-value>
</context-param>

CR076399

An exception is received when a Web service is unavailable.

Problem

If a Web service is unavailable at runtime, the portlet will throw an exception.

Platform

All.

Workaround

CR077546

Hitting browser refresh after creating a user causes an error indicating the user already exists.

Problem

When a new user is created for the first time in a portal, and the browser refresh is clicked to refresh the data on the page, the user is returned to the user login page with the message "user already exist". This is because the url is still in the browser that created the user. If you refresh the browser, it attempts to create the user again, resulting in the error.

Platform

All.

Workaround

A flag in com.bea.portal.appflow.processor.security. UserProcessor process( ) method can be set to redirect the user after the webflow reaches the postProcessor in the portal webflow. The portal webflow will need to change to direct the success event from the postProcessor to a new InputProcessor which detects if a redirect has been flagged.

If not, this InputProcessor will continue to the portal presentation node. If the flag has been set, it will forward to a new redirect presentation node which in turn redirects the user to the context root. Please contact support if you require this workaround.

CR078988

"Unable to find DocumentConnectionPool" message during startup

Problem

On servers where service configuration MBeans exist in application-config.xml but the server is not targeted, an exception similar to the following is displayed: weblogic.ejb20.WLDeploymentException: Unable to find DocumentConnectionPool 'default' configuration MBeanjavax.ejb.CreateException: Unable to find DocumentConnectionPool 'default' configuration MBean. This error will also occur if the DocumentManager EJB is configured to use a DocumentConnectionPool that hasn't been configured in the application-config.xml.

Platform

All.

Workaround

Use the Console to verify that the application's Service Configuration is targeted correctly, and make sure a DocumentConnectionPool MBean exists with the correct name.

CR077981

and

CR074989

Classpath changes are necessary for using WebLogic Builder with WebLogic Portal.

Problem

The WebLogic Builder tool from the WebLogic Server requires classpath insertions to use it against any WebLogic Portal EJBs.

Platform

All.

Workaround

call %WL_HOME%\portal\bin\win32\set-environment.bat

set P13N_EJB=%PORTAL_LIB%\p13n\ejb

set PORTAL_EJB=%PORTAL_LIB%\portal\ejb

set

P13N_EJBS=%P13N_EJB%\document.jar;%P13N_EJB%\ejbadvisor.jar;
%P13N_EJB%\events.jar;%P13N_EJB%\ldapprofile.jar;%P13N_EJB%
\mail.jar;%P13N_EJB%\p13n_util.jar;%P13N_EJB%\pipeline.jar;
%P13N_EJB%\placeholder.jar;%P13N_EJB%\property.jar;%P13N_EJB%
\rules.jar;%P13N_EJB%\usermgmt.jar

set

PORTAL_EJBS=%PORTAL_LIB%\portal\ejb\portal.jar;%PORTAL_LIB%
\portal\ejb\portal_util.jar

set WLP_EJBS=%PORTAL_EJBS%;%P13N_EJBS%

CR079253

Prior to Service Pack 4, group administrators who are deleted from entire system still appear in admin and admin eligible lists.

Problem

Users who are granted delegated admin capabilities and who are then deleted from the entire system via Portal User Management still appear in admin lists.

Platform

All.

Workaround

CR079504

Placeholders with relative links do not work when the proxy uses a prefix for the web application

Problem

Placeholders rendered from campaigns are using relative links. Any relative links that are generated in a Web application will not be properly displayed if a prefix for the proxy is set.

Platform

All.

Workaround

This problem can be fixed by changing the service configuration in your proxy. For example, when using the iPlanet proxy, edit the obj.conf file. Find the <Object name="default"> section and insert the following service method below the NameTrans entries:
Service method="(GET|HEAD|POST|PUT)" fn="wl_proxy"
WebLogicCluster="myServer1:7501,myServer2:7539"

CR079638

Sampleportal uses deprecated security-principal-map tag

Problem

The BlackBoxNoTx JCA connector used in sampleportal makes use of the deprecated security-principal-map JCA deployment descriptor tag to store security credentials. This results in the following warning on startup:

<m2Server> <main> <kernel identity> <> <190065> <Deprecated element

security-principal-map used for BlackBoxNoTx - Application: BlackBoxNoTx,

Module: BlackBoxNoTx, EIS Type: JDBC Database.>

The security-principal-map tag was deprecated in favor of storing the information in WebLogic Server's embedded LDAP server. Unfortunately there is no way to provide this information at installation time with the sample. Customers would have to configure the security credentials through the WebLogic Server administration console themselves. For this reason it was decided to leave the deprecated element in place.

Platform

All.

Workaround

If you want the warning message to go away, you can use the following procedure to configure embedded LDAP with the security credentials:

CR081979

Sybase 12.5 SWR 10235 does not work with WLP 7.0.

Problem

Data sync fails with a duplicate key violation.

Platform

All.

Workaround

Both Sybase 12.5 GA and 12.5.0.2/EBF 10573 do not display this problem. It has only been reproduced on SWR 10235. Therefore do not use SWR 10235 with WebLogic Portal 7.0 Service Pack 2.

CR082829

OutOfMemoryError when hundreds of thousands of items are placed in the shopping cart.

Problem

com.bea.commerce.ebusiness.price.service.internal.PriceServiceImpl throws an OutOfMemoryError when there are too many items in the shopping cart. This applies to both the number of line items and the number of product items in a particular line item.

Platform

All.

Workaround

Constrain the maximum number of line items and total items in your shopping cart and the saved list. As of Service Pack 4, the WebLogic Commerce Server and e2e examples were modified to add a ShoppingCartConstraints.java class with constants that set the maximum number of line items and total items.

The following PipelineComponent and InputProcessor classes were modified to use the new constraints: AddProductItemToShoppingCartPC, MoveProductItemToSavedListPCImpl, MoveProductItemToShoppingCartPCImpl, and UpdateShoppingCartQuantitiesIP. The source code is included with the WebLogic Commerce Server and e2e examples.

In addition, messages were added to ebusiness-shoppingcart.properties to be used when the constraints are exceeded.

CR083219

Searching for subgroups in the Admin Tools returns "group not found."

Problem

In User Management, searching for a subgroup results in a "group not found" message.

Platform

All.

Workaround

None; subgroups can only be displayed by expanding the parent group.

CR083497

In the wlcs sample, errors can occur if you delete customers and use the order service

Problem

If you delete a customer you may see the following error while using the order management JSP tools:

com.beasys.commerce.bridge.bmp.RowNotFoundException : Row not found for query
/SELECT WLCS_CUSTOMER.BUSINESS_PHONE , WLCS_CUSTOMER.LAST_NAME ,
WLCS_CUSTOMER.EMAIL , WLCS_CUSTOMER.MIDDLE_NAME , WLCS_CUSTOMER.FAX ,
WLCS_CUSTOMER.TITLE , WLCS_CUSTOMER.CUSTOMER_TYPE , WLCS_CUSTOMER.SUFFIX ,
WLCS_CUSTOMER.HOME_PHONE , WLCS_CUSTOMER.FIRST_NAME FROM WLCS_CUSTOMER WHERE
WLCS_CUSTOMER.CUSTOMER_ID = ?/ for class or Pk
/com.beasys.commerce.ebusiness.customer.CustomerDelegateImpl/ with primary key /{2}/.

Or the order management JSP administration tools will indicate that the customer ID for the order could not be found.

Platform

All.

Workaround

If you delete a customer you must purge or archive the order history for that customer. Otherwise you may receive exceptions when accessing the order containing the deleted customer.

CR084158

"localhost" is configured for sample tax and payment services

Problem

In the WebLogic Commerce Server Sample Application, an error occurs after clicking on the Use button for the Shipping Address or Credit Card Payment if you are not using localhost (for example, in a cluster).

Platform

All.

Workaround

Change the WSDL setting for the Tax Calculator WSDL and the Payment Web Service WSDL in the WebLogic Server Console to direct requests to the applicable machine name, or to the proxy in a cluster. This is done by navigating to the wlcsApp web a