This content has been marked as final. Show 7 replies
The config plan only helps you to change references, while building you SAR (.jar). However, your issue is to see the XSLT, e.t.c., at design time. Config plan don't help you in this situation. You have to find replace all your local WSDL references, make them refer to the wsdl from your mds (like oramds:/your wsdl path inside MDS).1 person found this helpful
Tip: The search option (ctrl + shift + f) will come handy for you, it will let you find something in the whole project/application.
This should solve your problem.
Thank you for the response
But those were two different que
my que was i need to deploy my project JAR file in different server, untill now the WSDL's were in my local project folder , but now i moved my WSDL's to MDS repositiory and want to deploy the project in different server( MDS folder present in another server ) untill now we used to Deploy in another server using config plan(when WSDL's are present in local project) but as the WSDL's are moved to MDS folder i am not getting the end point i need in server. can you please provide me the solution
should i have to move forward using Config plan or should i have to use different concept for changing the end point URL to Run in different server
The explanation is ambiguous (to me at least). Can you explain again.
S1 as Server one
S2 as Server two
P1 as Project one
P2 as Project two
RT as Run time
DT as Design time
As per as my knowledge is to be considered
the files which you are using in MDS should be there in the server where your project is running. .
you cant import the ora mds
so do one thing first redeploy the application which is pointing out your MDS in to the server where you are going to deploy the project
then you can import the files in the MDS, . . .
We have created a project P1 in S1 and want to deploy in S2 we want the WSDL to change it's end point Dynamically
at run time which is present in WSDL as Location. before using MDS we were using config plan to Search and replace option in config plan to change the end point but now as we don't have the WSDL in local now HOW TO CHANGE THE LOCATION IN WSDL SO THAT IT POINT TO S2
Like others, I am not really sure, if I have got that correctly.
But I would give my 2 cents here.
You can keep your wsdl wherever you want.
I guess, you are referring to Concrete wsdl which contains the URL of the service in the binding section.
You can either do a find and replace on the wsdl being referred or you can use a "endpoint url" property in "composite.xml" and then, enter the endpoint url there.
1 person found this helpful
we want the WSDL to change it's end point Dynamically at run time which is present in WSDL as Location
HOW TO CHANGE THE LOCATION IN WSDL SO THAT IT POINT TO S2Looks like you have placed the Concrete WSDL in MDS, based upon the above two statements. In general this is a bad practice. The best practice is to always save an abstract WSDL in MDS. This is the solution for your problem.
Further, in the composite.xml you have to refer the abstract wsdl for design time and concrete wsdl for run time.