Naming Collisions in Trusted Domains?

Question

Hi all,
I am trying to have two WLS instances communicate with each other via JMS. The basic setup is working but now I want to add security to it. After adding User rstrictions as policies to the Queues I received error messages on the remote instance that it could not connect to the JMS resources defined on the local instance via the defined foreign jndi provider. This seemed logical as the two domains did not trust each other, so I created a Trusted domain between them.
But now i receive warnings on the remote instance that a filestore (which is defined on the local instance to persist the JMS messages) is not "assigned to any of these servers: adminserver". Which is wrong in my opinion since the server of the local instance is called 'adminserver' and the file store is targeting it.
On the other hand, the server of the remote instance is also called 'adminserver', now I am wondering if this naming conflict is the cause of the warning and more important if there might be other more severe problems that could arise from this situation?
Is there a solution for this problem apart from creating a new instance with a differently named server? To my knowledge it is not possible to rename a server once it is created.
Thanks, Chris

Answer 1

Communicating domains normally must minimally have different domain names, and, in most cases, must not have any server names in common. In addition, it's sometimes necessary to make sure that there are no JMS server names in common either. I've been able to change names by first shutting all servers down, and performing a search-and-replace in the config.xml.
I don't recommended changing the names in production setups without very careful planning. For one, there may be persistent data that references the old names (for example, the file names of each server's default file store are generated based on the server's file name).
Tom