Skip to Content
author's profile photo Former Member
Former Member

Problems release Webservice for SOAP runtime to a non-modifiable client


I created a webservice definition ( virtual interface & all dependent objects ) in a development client ( client- A ) of a ECC5.0 instance.

Now, we have another client ( client-B ) in the same server that we want to release the webservice for SOAP runtime. ( reason is that the webservice is not available at runtime in this client-B client )

This client-B has status - non-modifiable and hence cannot use WSCONFIG --> create option to release it for runtime.

How do we release this webservice definition to client - B . I tried a SCC1 transaction on client-B pointing to the transport that contains the WS definition in client-A. I got dictionary errors indicating that the WS definition objects are all client independent.

Is there something I am missing ? Any thoughts/similar experiences shared is appreciated.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Mar 31, 2008 at 06:11 PM

    I haven't experienced anything like it, but easiest way to solve this, is to set this client open for change.

    Add a comment
    10|10000 characters needed characters exceeded

    • Good to hear it worked out for you. But like I already said, I haven't experienced anything like this, but for similar problems this is exactly what we did to solve it. But you're probably right, that this is no long term solution. There should be another way of doing this, but no experience in that field expertise.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.