|
|
|
|||||
|
IceGrid 3.0 Admin migration
Unlike IcePack.Admin, IceGrid.Admin does not have addServer() and removeServer() methods. I'm trying to figure out what I need to do to migrate. Neither he 3.0 manual migration guide nor the article about IceGrid migration in the latest issue of Connections mentioned what to do here. I noticed there is an instantiateServer call in 3.0, but it is for "instantiating server templates" which we do not use and the args are vastly different from the old addServer(). In our old call to addServer() we are specifying a node name, serviceName, descriptor file name, and target list.
As far as removeServer() migration, there is a removeServers sequence in the NodeUpdateDescriptor used by the ApplicationUpdateDescriptor set by the IceGrid.Session.updateApplication() method. Is this what we should use now? The old removeServers() call did not require a node name, but just a server name. Is there some other way to remove a server just by name? I saw that icegridadmin still allows one to do this. Perhaps I missed something in the docs so feel free to point me to existing info. Any help would be greatly appreciated. Thanks, Brian |
|
|||||
|
Thanks for the response, Benoit. I think I figured out how to use updateApplication to remove a server. But can't comprehend how to do so for adding a server. Both ApplicationUpdateDescriptor and NodeUpdateDescriptor have Api for only removing or listing current servers, but not adding. I guess I need more help or a pointer to more example code.
Thanks, Brian |
|
||||||
|
Hi Brian,
You should use the servers attribute of the NodeUpdateDescriptor structure. You can either add or update a server by adding the server descriptor to the servers sequence. Something along the lines of the following should make the job: Code:
NodeUpdateDescriptor nodeUpdate; nodeUpdate.name = <name of the node>; nodeUpdate.servers.push_back(<your new server descriptor>); ApplicationUpdateDescriptor update; update.name = <name of your application>; update.nodes.push_back(nodeUpdate); IceGrid::AdminPrx admin = /* proxy to IceGrid::Admin object */ admin->updateApplication(update); (contact sales@zeroc.com if you need more information on our consulting services).Benoit. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| I can't find ICEGrid GUI Admin tool | mic_lee2000 | Help Center | 4 | 11-25-2006 08:16 AM |
| IceGrid migration issue: icegridadmin can't reach registry | brian | Help Center | 1 | 12-15-2005 03:12 PM |
| 'Transparent' Object Migration Granularity | seth.piezas | Help Center | 4 | 02-17-2005 03:47 PM |
| starting "ice" process (node/admin etc) via Java | BobDeAnna | Help Center | 6 | 01-04-2005 10:26 AM |
| load balancing/fault tolerance/object migration | rc_hz | Help Center | 0 | 11-22-2004 02:03 AM |