Can't access registered services in gateway cockpit after setting proxies

[Jitendra_Kansal]

Hi Experts,

We wanted to access one publicly available WSDL through one proxy network by creating OData modeling. But we were not able to deploy the same from Eclipse to Integration gateway cockpit. So we set the proxy settings in the props.ini file available in SMP3 SP03 server path as per Ali's blog

Now everything works fine , including OData model deployment to SMP server, accessing service document, metadata document.

But, there are few already deployed services in gateway cockpit, when i tried to access them, i get this error in a browser:

<error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">

<code/>

<message xml:lang="en">

Could not instantiate data provider based on class null

</message>

</error>

Also, When i tried to deactivate the registered services, i get this message:

Even, if i try to redeploy existing service from Eclipse by giving different version no, it is not updating in the registered service list.

To work for the same service, i had to recreate everything from scratch which was painful.

What could be the reason for this issue? Proxy settings?

,

Regards,

JK

[Jitendra_Kansal · Accepted solution]

problem resolved.

Before executing these commands, smp related service should be stopped.

Execute this svcutil -uninstall
Execute this svcutil -generate
Execute this svcutil -install

Rgrds,

JK

[Former Member · Accepted solution]

I'm seeing the same problem. I tried stopping the SMP service and executing those commands but still getting the Could not update service message.

Anything else I can try? Do you know what the root problem is?

Thanks!

DJ

[Jitendra_Kansal · Accepted solution]

Hi DJ,

I have seen some strange behaviors with above approach.

after setting proxies on two different smp sever machines,  On one machine i am able to run the already deployed OData service  through GW cockpit but on other machine if i run an already deployed OData service then i see the above error.

Rgrds,

JK

[Former Member · Accepted solution]

Re-deploying the service from GWPA seemed to work for me. Hopefully they will bring more stability to the platform.