A
Adrian B.
Hi,
I've created a PSI extension, and successfully used Colby Africas tool to
deploy the PSI extension....but only on the server hosting the SSP (ie the
PSI).
I read the MS PSI Extension how to and figured that all I had to do for the
other WFE servers was copy the wsdl and disco (aspx) files into same location
(under the \12\ISAPI\PSI). This didn't seem to work.
I can access the web services via the SSP path
(ie http://ipmotest002:56737/Shared Services/PSI/IpmoExtensions.asmx) but
no via the PWA path (ie
http://project.ipmotest.local/pwa/_vti_bin/PSI/IpmoExtensions.asmx)
I just get a
Description: http 404. The Resource can not be found, blah blah
Requested Url: /Shared Services/PSI/IpmoExtensions.asmx
As mentioned this work if I have a single WFE server.
Any ideas?
Adrian
I've created a PSI extension, and successfully used Colby Africas tool to
deploy the PSI extension....but only on the server hosting the SSP (ie the
PSI).
I read the MS PSI Extension how to and figured that all I had to do for the
other WFE servers was copy the wsdl and disco (aspx) files into same location
(under the \12\ISAPI\PSI). This didn't seem to work.
I can access the web services via the SSP path
(ie http://ipmotest002:56737/Shared Services/PSI/IpmoExtensions.asmx) but
no via the PWA path (ie
http://project.ipmotest.local/pwa/_vti_bin/PSI/IpmoExtensions.asmx)
I just get a
Description: http 404. The Resource can not be found, blah blah
Requested Url: /Shared Services/PSI/IpmoExtensions.asmx
As mentioned this work if I have a single WFE server.
Any ideas?
Adrian