|
Problem(Abstract) |
There are some documented differences between WSAdmin and
the Administrative Console. |
|
|
|
Resolving the
problem |
URL Rewriting doesn't come to effect after wsadmin script
invocation , whereas the config change in "Session Management" of
application comes into effect when this change is done through
administrative console.
- When installing an application to a cluster through the administrative
console, at step #11 Map modules to application servers, choose cluster1
in cell S1EMCLC1, the following server name:
WebSphere:cell=S1EMCLC1,cluster=cluster1
However, when installing the application through wsadmin scripting
specifying the cluster as follows:
$AdminApp installInteractive /IBWJ/ears/WPCPVTBEARApr24.ear {-cluster
cluster1}
It automatically maps the modules to a different server name, where
S1ENLC1 is the node where one of the clustered servers lives:
Module: PVTBMDB
URI: PVTBMDB.jar,META-INF/ejb-jar.xml
Server: [WebSphere:cell=S1EMCLC1,node=S1ENLC1,cluster=cluster1]:
Module: WPCPVTBEJB
URI: WPCPVTBEJB.jar,META-INF/ejb-jar.xml
Server: [WebSphere:cell=S1EMCLC1,node=S1ENLC1,cluster=cluster1]:
Module: WPCPVTBWeb
URI: WPCPVTBWeb.war,WEB-INF/web.xml
Server: [WebSphere:cell=S1EMCLC1,node=S1ENLC1,cluster=cluster1]:
- $AdminConfig list type scope ignores every scope that is more specific
than node. WebSphere Portal configuration makes use of $AdminConfig list
type scope using server IDs as scope objects. On IBM® WebSphere®
Application Server distributed, it correctly returns all objects of the
given type in the scope of the server ID. On Application Server z/OS, it
returns all objects of the given type in the scope of the server
node.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|