Deployment with Deployment manager

0
votes

I am trying to auto-deploy an application to a newly installed Websphere ND with Deployment Manager. This is what I just did:

  1. Install WebSphere
  2. manageProfiles create, profile name="deployer", template = management, profile type = DEPLOYMENT_MANAGER, cell="ndcell", node="ndnode"
  3. manageProfiles create, profile name="app", template = default, cell = knowncell, node = knownnode
  4. AppServer/profiles/deployer/bin/startManager.sh
  5. AppServer/profiles/app/bin/addNode.sh hostname (this all happens on one same host "hostname")
  6. AppServer/bin/wsadmin -c '$AdminConfig modify [$AdminConfig showAttribute [$AdminConfig getid /Cell:ndcell] monitoredDirectoryDeployment] {{enabled true}}' - turn on monitored directory deployment
  7. AppServer/bin/wsadmin -c '$AdminConfig save'
  8. AppServer/profiles/deployer/bin/stopManager.sh, then startManager.sh

All right, at this point admin console shows one server "server1" which is not started, and there exists the directory AppServer/profiles/deployer/monitoredDeployableApps, that's the good part. The bad part is the directory is empty! There is no "server1" dir there, as it should be, to put my EAR into.

What am I missing?

1
webspherewebsphere-8
I'm assuming by "cell = knowncell, node = knownnode" you meant "cell = ndcell, node = ndnode"? - F Rowe
No it's different cell/node. On addNode, the node gets injected into ndcell anyway, isn't it? I thought if I created server1 in ndcell initially, adding it to a cell would have no sense, since it's already in that cell. Did I get that wrong? - Maksim Gumerov
But thinking of it now, does executing addNode mean that "app" profile now belongs to cell ndcell instead of knowncell? - Maksim Gumerov

1 Answers

1
votes

You have to do a full synchronize in order to Dmgr deem changes to take effect