cancel
Showing results for 
Search instead for 
Did you mean: 

NWDI Configuration Update Problems in CMS

Former Member
0 Kudos

Hi,

We have done a heterogeneous migration of JDI from AIX to HPUX.

I started doing the post steps for JDI. I could successfully change the configuration parameters in the DTR (for name server, repository) and CBS (in visual Admin) to reflect the new target system names.

But when i tried to edit the configuration in the CMS, like i edited the CMS URL in the "Domain Data" and clicked "Save Domain". It could save successfully. But when i tried to do "Update CMS" it gave me the following error.

"DTR (URL http://<old JDI host name>:54000/dtr) server exception: Communication problems occured with repository "http://<old JDI host name>:54000/dtr". Unable to open connection to host "<old JDI host name>:54000". The IP address of the host could not be resolved. Maybe the URL is misspelled or the host does no longer exist.."

Also in the "Track Data" when im trying to change DTR and CBS URL's to reflect the new target systems, it is giving the following error "Unexpected error; inform your system administrator: communication error: connection/authorization problem to host http://<old host name of EP>:54000 user: administrator

Im not sure whereelse should i change the URL's of these, so that i dont get any error when updating the URL's in CMS.

Any suggestions are welcome.

Thanks

Sourav

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

hi.Do you have the DTR configuration document? Could you send it to me?

Former Member
0 Kudos

No, I dont have any document in speciifc for DTR configuration...

Former Member
0 Kudos

solved the problem...

Former Member
0 Kudos

Hi,

We are also getting the same problem... Please could you let me know how did you solved?

Thanks & Regds,

Jithendra

Former Member
0 Kudos

Hi Jithendra,

This is a bug in JDI. you need to open a ticket with SAP provding connection to your database so that SAP can login and do changes in the DB level. The sap note for this problem has not been released yet so you need to open a ticket with them.

Thanks

Sourav

Former Member
0 Kudos

Thanks Sourav