|
>Q1. Is there any method of adding some tasks to a existing task server except
>the server recreation? The recreation sometimes changes the object UUID, and
>it makes the client unable to call the server tasks.
V3.0 has a new "recreate server command" that helps somewhat, but not with
the object UUID problem. When a task server starts, it checks it's own name
space entry to see if an object UUID exists, and if it does, it reuses it.
If the object uuid does not exist, such as when the server is created and
run for the first time, then a new object UUID is created.
>Q2. Why is the object UUID of the task server sometimes changed by the
>recreation?
When a server is deleted, so is it's namespace entry. So when the server is
restarted, it doesn't find an already existing object UUID (see above).
>Q3. Is there any way to communicate the client with the server even if the
>server object UUID in the client local copy is old?
I'm not aware of any way. Perhaps someone else has an idea?
>Q4. We are planning to construct a customer system which consists of about 20
>servers (VMS and WNT) and a few hundred PC clients. (So, I'm trying ACMSxp.)
>We don't want to type the rpccp show server -u command on a few hundred PCs
>when some tasks are added to a existing task server. Any other good ideas
>would be appreciated.
One thing you could try is to make sure the client and server systems are in
what DCE calls "broadcast range" of one another. When you configure the client
into the cell, if DCE can find the cell with out you having to type in the cell
name, then you are in broadcast range. When this happens, no local cache is
created so you won't have to update the clients using rpccp show server -u. When
the server's object uuid changes, the client picks it up dynamically. As best as
I can tell, broadcast range is close to being on the same TCP/IP subnet, but
I've seen cases where the client didn't think the cell master was in broadcast
range even though the master and the client were on the same piece of thin wire
and on the same subnet!
|
| Vineleaf-san,
>When a task server starts, it checks it's own name space entry to see if an
>object UUID exists, and if it does, it reuses it. If the object uuid does not
>exist, such as when the server is created and run for the first time, then a
>new object UUID is created.
Thanks for your good suggestion!
Today, I deleted a task server and confirmed that its name space entry was
deleted. After that I recreated the server. Before starting the server, I
executed the rpccp export -o command with the old object UUID.
When the task server started, the task server used the old object UUID.
Yeah!
Please advise me if this method is not good.
|
| Horie-san,
> Please advise me if this method is not good.
I can't see any harm in what you are doing. You are manually populating the
namespace, but there's no real difference between you doing it vs. ACMSxp
doing it. So if it works, continue to use your technique.
We are investigating ways that will not require you to manually export the
binding information. That is, the client will try to effectively do an "rpccp
show server -u" for you. Thank you for bringing this to our attention.
Ken
|