| Author |
Portal and WAS deployment manager
|
|
|
| I have a development environment with WPS V5.1.0.1 running on a WAS V6.0.1.2 standalone node. I also have a WAS V6 deployment manager that already has a non-portal node deployed to it. Does anyone know of any issues/problems if I federate the node with
WPS installed into this cell? I seem to recall IBM recommending not to mix portal and non-portal nodes in the same cell.
| |
|
| I just federated a WPS5.1.0.1 node running on WAS 6.0.1.2 with a dedicated deployment manager and I had problems where the Portal server was looking for wmm.xml in \AppServer\profiles\server1\config\wmm\w
mm.xml. At this point, I'm waiting to hear from IBM
support to determine what to do next.
Do you have any install procedures for the WPS5.1.0.1/WAS6.0.1.2 setup that you would be willing to share? I'm trying to set up a similar configuration and am having problems because I can't see the WebSphere_Portal server in the admin console - this is t
he whole reason why I tried to set it up with deployment manager.
| |
|
| <Paul.Munsen@nav-international.com> wrote:
> I just federated a WPS5.1.0.1 node running on WAS 6.0.1.2 with a dedicated
deployment manager and I had problems where the Portal server was looking for
wmm.xml in \AppServer\profiles\server1\config\wmm\w
mm.xml. At this point, I'm
waiting to hear from IBM support to determine what to do next.
> Do you have any install procedures for the WPS5.1.0.1/WAS6.0.1.2 setup that
you would be willing to share? I'm trying to set up a similar configuration
and am having problems because I can't see the WebSphere_Portal server in the
admin console - this is the whole reason why I tried to set it up with
deployment manager.
| |
|
| Tony wrote: After federating your portal node to Dmgr then you need to do
the following 2 steps in order for it to work:
1- Edit the <wps_root>/config/wpconfig.properties and change the CellName
and verify the PrimaryNode properties:
CellName=<cell_name>
Example:CellName=<dmgr_node>Network
The cellname changed during federation of the Node 1. To verify the
cellname you can identify it by
<wsas_profile_root>/config/cells/<cell_name>
PrimaryNode=<true or false> If this node is the primary portal node then
set it to true.
2- Run the post-portal-node-federation-configuration task by issuing the
following command:
<wps_root>/config/WPSconfig.bat post-portal-node-federationconfiguration
> <Paul.Munsen@nav-international.com> wrote:
> deployment manager and I had problems where the Portal server was looking
for
> wmm.xml in \AppServer\profiles\server1\config\wmm\w
mm.xml. At this point,
I'm
> waiting to hear from IBM support to determine what to do next.
> you would be willing to share? I'm trying to set up a similar configuration
> and am having problems because I can't see the WebSphere_Portal server in
the
> admin console - this is the whole reason why I tried to set it up with
> deployment manager.
|
|
|
|