Domains

Hi All,

Can JDEdwards E1 (8.9) support dual domains? That is, can I have enterprise and deployment servers in one domain and citrix servers on a different domain? There will be no firewall between these domains. I have a need to set it up this way. If not I will look at alternate route.

-Sam

E18.9, TR8.96_H1, Oracle 10G

Yes.

OneWorld doesn't have anything to do with NT Security or Active Directory. The only issue would come with 8.9x and Single Sign On if you were using tokens - but a trusted domain would take care of that issue.

Oneworld sees resolved names - so even IP addresses can change. Server Names, however, are a little tougher to change (lots of comments about that subject in JDEList !)

I finally had time to install the client on a different domain from that of deployment server. Installation went fine but when I try to login it gives me security authentication error. I do a GET AUTH and it still does not get the code.

I installed a client in the same domain as deployment server, everything works fine and am able to log in. Obviously I have to make the domain name apparent to the client but I do not know where. I set the registries to have fully qualified name and still no luck.

Have anybody tried this?

Thanks,
--Sam

Sam,

Do you have full trust between the domains? If so, that will work. I have users from three different domains accessing my servers. As Jon said in his post, JDE doesn't know or care about domains, but your domains need to have a trust relationship.

Thanks. I will check on that. I don't think we have full trust between these domains.

Hey, You first access your deployment server from your FAT client using START --> RUN and then try to click GET.
Hopes this will work.

Hey, just access your deployment server from client using START--> RUN and then try to Click GET.
Hopes this will work.

Now I have full trust between domains and it still does not work. The DNS name of the deployment server is pad01psd01.padsolutions.com. But the logs show only the DS name. All the registries on the client have fully qualified deployment server name. It looks like during login JDE gets the DS name from F00945 where it is not fully qualified in my case because of the 15 character limitation.
Is your fully qualified name less than 15 characters?
------
Opening up remote metadata repository. Type - JDESPECTYPE_JDECLIENT, Path - \\PAD01PSD01\B9\CLIENT\
Jan 09 15:55:26.377001 - 5772/5160 WRK:Starting jdeCallObject TAM: tamfopen \\pad01psd01\b9\client\jdeclntuni.xdc error 53-The network path was not found. WinErrNum=53.
Jan 09 15:55:26.486000 - 5772/5160 WRK:Starting jdeCallObject TAM: tamfopen \\pad01psd01\b9\client\jdeclntuni.xdc error 53-The network path was not found. WinErrNum=53.
Jan 09 15:55:26.596000 - 5772/5160 WRK:Starting jdeCallObject TAM: tamfopen \\pad01psd01\b9\client\jdeclntuni.xdc error 53-The network path was not found. WinErrNum=53.
Jan 09 15:55:26.596002 - 5772/5160 WRK:Starting jdeCallObject TAMInitX (\\pad01psd01\b9\client\jdeclntuni.xdc): Error opening index file "\\pad01psd01\b9\client\jdeclntuni.xdc" : WinErrNum=0. No such file or directory. Std C errno=2.
Jan 09 15:55:26.596004 - 5772/5160 WRK:Starting jdeCallObject JDESPEC0000027 - TAM init failed!

Now I have full trust between domains and it still does not work. The DNS name of the deployment server is pad01psd01.padsolutions.com. But the logs show only the DS name. All the registries on the client have fully qualified deployment server name. It looks like during login JDE gets the DS name from F00945 where it is not fully qualified in my case because of the 15 character limitation.
Is your fully qualified name less than 15 characters?
------
Opening up remote metadata repository. Type - JDESPECTYPE_JDECLIENT, Path - \\PAD01PSD01\B9\CLIENT\
Jan 09 15:55:26.377001 - 5772/5160 WRK:Starting jdeCallObject TAM: tamfopen \\pad01psd01\b9\client\jdeclntuni.xdc error 53-The network path was not found. WinErrNum=53.
Jan 09 15:55:26.486000 - 5772/5160 WRK:Starting jdeCallObject TAM: tamfopen \\pad01psd01\b9\client\jdeclntuni.xdc error 53-The network path was not found. WinErrNum=53.
Jan 09 15:55:26.596000 - 5772/5160 WRK:Starting jdeCallObject TAM: tamfopen \\pad01psd01\b9\client\jdeclntuni.xdc error 53-The network path was not found. WinErrNum=53.
Jan 09 15:55:26.596002 - 5772/5160 WRK:Starting jdeCallObject TAMInitX (\\pad01psd01\b9\client\jdeclntuni.xdc): Error opening index file "\\pad01psd01\b9\client\jdeclntuni.xdc" : WinErrNum=0. No such file or directory. Std C errno=2.
Jan 09 15:55:26.596004 - 5772/5160 WRK:Starting jdeCallObject JDESPEC0000027 - TAM init failed!

Can you ping just the DS name? If so, I'm not sure what your issue could be. However, if you can't, maybe try an entry in the host file.

It may not be a very good permanent fix, but may work until you can work with your network admins to get it resolved.