Rehosting Question

[srector]

So……I was feeling quite proud of myself after completing my first rehosting exercise. The system came up, I can log in. I can navigate from page to page. I can even open and/or download documents.

What I can’t seem to do, however, is perform a search.

Every time I submit a search, the system throws the following error:

---

Server Exception: (com.infoengine.util.IEResource/..)

com.infoengine.au.NoSuchServiceException:

No such service: .corp.drs-sts.pdmtest.Windchill.

---

I have gone over and over the rehost procedure and haven’t been able to find my mistake.

I have deleted the Apache/Tomcat/Windchill caches. Rebuilt the Jar files, and re-propagated the property files using ‘xconfmanager –p’.

And still I get this error message.

If anyone has any ideas on where I should look next, I’d appreciate the tip.

Thanks!

Steve

[wpalm_99]

Steve,

Go to the Info*Engine Administrator
Pick the Task Delegate Administration link
Pick Manage Repository
For each Repository Name in the drop down list, make sure you have the
Windchill adapter picked for Webject Processor and Task Processor, and then
pick Update once they're selected

This should take care of that issue. This almost always happens if you
have a different number of MSs running on the source and target systems.
It also sometimes just happens anyway.

Regards,
Bill



On Tue, Aug 14, 2012 at 6:26 PM, Steven Rector <steven.rector@drs-sts.com>wrote:

> So……I was feeling quite proud of myself after completing my first
> rehosting exercise. The system came up, I can log in. I can navigate from
> page to page. I can even open and/or download documents.
>
> What I can’t seem to do, however, is perform a search.
>
> Every time I submit a search, the system throws the following error:
>
> * *

[srector]

So, after three weeks of persistent digging, I finally figured out why the search function wasn't working.

In the file:

- - - \codebase\WEB-INF\web.xml

There were four lines that still referenced my old server. The parameters involved were:

<param-name>config.myName</param-name>

<param-name>config.namingServiceName</param-name>

Correcting these lines and restarting the services cleared the problem.

Many thanks to Steven Ko who posted the information back in Sept. 2011!