OSB Server restart

Hello,
I made some changes to WSDLs and Service using OSB web console in Admin server. The Admin Server has two managed servers.
When I activated the changes, it says "Server(s) require restart before session can be activated."
Similar action I performed in other env got immediate effect without prompting for server restart.
Could you please tell me what are the cases that server(s) restart are required when changes are made via osb console.
Thanks

You would get that message in Service Bus Console if you made any non-dynamic configuration changes earlier through Weblogic Console and didn't restart the server. The reason for this behavior is as follows:
Changes to non-dynamic configuration attributes require that the affected servers or system resources be restarted before they become effective. If a change is made to a non-dynamic configuration setting (For exampl, certain JMS configuration modification), no changes to dynamic configuration settings will take effect until after restart. This is to assure that a batch of updates having a combination of dynamic and non-dynamic attribute edits will not be partially activated.
For details, please refer to Weblogic Administration guide in the link below and look at the section for dynamic and non-dynamic changes.
http://download.oracle.com/docs/cd/E15051_01/wls/docs103/intro/console.html
Hope this helps.

Similar Messages

OSB server is going in health warning state.

I am getting following log entries in my os b log file
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393574> <BEA-149059> <Module ejb.jar of application _ALSB_1352206034075 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393579> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-990041227111414011--6d1116fb.13ad527984a.-7fe9>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393579> <BEA-149060> <Module ejb.jar of application _ALSB_1352206034075 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393854> <BEA-149059> <Module ejb.jar of application _ALSB_1352206034484 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393858> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-990041227111414011--6d1116fb.13ad527984a.-7fe8>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393858> <BEA-149060> <Module ejb.jar of application _ALSB_1352206034484 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:54 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567394738> <BEA-149059> <Module ejb.jar of application _ALSB_1352206034835 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:54 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567394742> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-990041227111414011--6d1116fb.13ad527984a.-7fe7>
####<Feb 4, 2014 9:29:54 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567394743> <BEA-149060> <Module ejb.jar of application _ALSB_1352206034835 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395022> <BEA-149059> <Module ejb.jar of application _ALSB_1359865966296 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395045> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-4841502376605855591--128e0c06.13c9db0f17e.-7fcf>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395045> <BEA-149060> <Module ejb.jar of application _ALSB_1359865966296 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395088> <BEA-149059> <Module ejb.jar of application _ALSB_1371011239470 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395090> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-8090345450005809436-74582d1.13f09f8a361.-7fe1>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395090> <BEA-149060> <Module ejb.jar of application _ALSB_1371011239470 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395100> <BEA-149059> <Module ejb.jar of application _ALSB_1371024065613 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
lastly its not giving message of successful transition and health of the server goes in warning state even restarting resolve it for some time. and again its move to warning state kindly help with the reason and reolution

Hi,
As Ros mentioned earlier you need see whether server logs have stuck thread or also check whether your Heap is trying to reach Max .
also might be your services have any problem.
So you need to check your OSB server logs.
Regards,
Kal

OSB server

Dear team,
We have configured remote OSB server(11.1.14 version) in OEPE workshop(installed in local machine) and we tried to start remote OSB server for first time.. The OSB server status is Started,republish.
Is it like for the first time after server configuration and starting for first time , workshop status should be like started,synchronized.
When we tried to deploy OSB configuration project to remote server, we are getting the below error:
"Conflicts found during publish" error.
We have cleaned the project and restarted the eclipse and created the new configuration project, still we are getting the same problem.
please suggest.
Regards,
radha
Edited by: user11189306 on Apr 19, 2012 10:07 PM

Hi Radha,
Is there any project when you open up sbconsole (http://localhost:7001/sbconsole, your URL might be different) having the same name as the one in Eclipse? If so, please delete that and then try publishing it from Eclipse.
If that's also failing, then there might be some resource that is being referenced in your project but not available as of now. Check that please.
Do you get any well defined error while publishing? If so, please post it here so that we can debug it better.
Regards
Swagat

JDBC Connection pool recovery after DB server restart

I am finding that Kodo is throwing the following exception after I restart
my database server (mysql). I am doing the database server restart while my
application server is idle, so it is not during a transaction.
Communication link failure: java.net.SocketException [code=0;state=08S01]
NestedThrowables:
com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code? For example, WebLogic Server's JDBC connection pool has a setting that
enables testing a connection and recovering from such failures before
allocating it from the pool.
Ben

This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code?Not right now. You can log an enhancement request with our bug database:
http://bugzilla.solarmetric.com/

BPEL Server Restarts intermittently

Hi All,
I have got a strange problem with my BPEL Server. Every once in a while the BPEL Server restarts on its own. I do not know if it has to do something with memory leaks or performance or some other reason.
I have made my logs to roll at every 2 GB. I also noticed that the BPEL Domains are reloaded everytime the logs are rolled. If during this restart there is some process on the go then i get erroneous results.
I am not able to reproduce the issue but it does happen intermittently. Has anyone else faced this issue?

Also check logs in $OAS_HOME/opmn/logs/ for "Restart" messages, then check the timeouts for the BPEL instance in $OAS_HOME/opmn/config/opmn.xml. These are maybe too low.
--olaf

PI 7.0 Production server restarts automatically

Hi guys,
We have installed and configured correctly a PI 7.0 system on Windows 2003 Standard Edition X64-bit with SQL Server 2005. We are on SP12. Everything, SLD, RFC connections work properly.
The problem is that 4-5 days after the installation the Windows Server restarts automatically in unexpected time during the day (unexpected shutdown), even when anybody doesn't do anything in the system. In the Event Viewer we get the following message/error "System Error: Category 102 EventID 1003". There are no other messages/errors.
This is a production system and we are supposed to go live within the next days! So I need your help ASAP.
Any ideas?
Thank you.
Best Regards.
Evaggelos

1) update your network card drivers to the latest and for all devices including your motherboard chipset drivers.
2) Are you using ethernet instead of USB?
3) This URL might help you
http://www.pcreview.co.uk/forums/thread-1885463.php
Regards
Sangeetha

How to get server name and port of OSB server in a proxy service ?

I need to get the server name and port of the OSB server inside a proxy service. How can I get this?

You may use java callout for this purpose -
How to get ServerName and ApplicationName in OSB (ALSB) ?
Regards,
Anuj

Canceling timers after server restart

hi,
i create a couple of timers. while the application server is up i can cancel them by getting the TimerService object of the bean it's associated with, calling getTimers() and cancelling the Timer objects returned from it.
if i restart the server (let's say it crashed), the timers created in the previous session are back to run - they are persistent by definition. but now i can't cancel them anymore: same getTimers() returns an empty Collection. i think this happens because the old timers from the previous session were not rebound to the new ejbcontext, or something like this.
my question is: how can i cancel timers, that were re-invoked after server restart.
thank you.
Message was edited by:
cyclid

Below are my tests that show canceling of timers working as expected:
Session bean methods:
public void createTimers()
{      System.out.println("### CREATE - a single-action timer that expires in 4s");
ctx.getTimerService().createTimer(4000, "single-action timer that expires in 4s");
System.out.println("### CREATE - an interval timer that expires in every 2s");
ctx.getTimerService().createTimer(2000, 2000, "interval timer that expires in every 2s");
public void cancelAllTimers() {
     System.out.println("### CANCEL - timers:");
     for (java.util.Iterator iter = ctx.getTimerService().getTimers().iterator(); iter.hasNext();) {
          Timer timer = (Timer) iter.next();
          System.out.println(" canceling ... " + timer.getInfo());
          timer.cancel();
public void logCurrentTime() {
     System.out.println("### CURRENT TIME - " + java.util.Calendar.getInstance().getTime());
public void ejbTimeout(Timer timer)
{     System.out.println("### EJB TIMEOUT - " + timer.getInfo());
Java Client test:
ejb.cancelAllTimers();
Thread.sleep(4000);
ejb.logCurrentTime();
ejb.createTimers();
Thread.sleep(8000);
ejb.cancelAllTimers();
ejb.logCurrentTime();
Thread.sleep(8000);
ejb.logCurrentTime();
Logs:
1. Shutdown servers while there is an interval timer
The log shows the interval timer came back and then was cancel after server restart
07/02/06 13:46:23 ### CANCEL - timers:
07/02/06 13:46:27 ### CURRENT TIME - Tue Feb 06 13:46:27 EST 2007
07/02/06 13:46:27 ### CREATE - a single-action timer that expires in 4s
07/02/06 13:46:27 ### CREATE - an interval timer that expires in every 2s
07/02/06 13:46:29 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:46:31 ### EJB TIMEOUT - single-action timer that expires in 4s
07/02/06 13:46:31 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:46:32 Shutting down OC4J...
C:\oc4j\10131_061009\j2ee\home>java -jar oc4j.jar
07/02/06 13:48:12 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
07/02/06 13:48:13 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:15 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:17 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:18 ### CANCEL - timers:
07/02/06 13:48:18 canceling ... interval timer that expires in every 2s
07/02/06 13:48:22 ### CURRENT TIME - Tue Feb 06 13:48:22 EST 2007
2. Cancel timers right after they were created
07/02/06 13:50:11 ### CANCEL - timers:
07/02/06 13:50:15 ### CURRENT TIME - Tue Feb 06 13:50:15 EST 2007
07/02/06 13:50:15 ### CREATE - a single-action timer that expires in 4s
07/02/06 13:50:15 ### CREATE - an interval timer that expires in every 2s
07/02/06 13:50:17 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:19 ### EJB TIMEOUT - single-action timer that expires in 4s
07/02/06 13:50:19 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:21 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:23 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:23 ### CANCEL - timers:
07/02/06 13:50:23 canceling ... interval timer that expires in every 2s
07/02/06 13:50:23 ### CURRENT TIME - Tue Feb 06 13:50:23 EST 2007
07/02/06 13:50:31 ### CURRENT TIME - Tue Feb 06 13:50:31 EST 2007

Xsan 2 MDC server restart hangs

Xsan 2 MDC server restart/shutdown hangs and I am forced to do a manual shutdown everytime. Here is the log when trying to do a restart or shutdown
10/16/08 2:58:43 PM loginwindow[58] ERROR | -[ApplicationManager(AppleEventHandling) _tryQuitAllForRequestor:replyEvent:] | _tryQuitAllForRequestor - vproc_set_global_ondemand returned error -1787534507
Running:
Xserve 2x3GHz Multi-Core 4GB RAM
Running OS X S 10.5.5
Xsan 2.1 (184)
Also if I try to do a terminal reboot command the server will panic.
Message was edited by: spraguga

Do you have more than one controller? Does the volume failover? Have you tried reinstalling the OS on this particular Xserve?

Deployed Files getting overwritten every time when I do a server restart

Hi,
I have deployed a web application in weblogic server. For testing purpose, instead of placing the changed file inside the war our team will change the files directly in the deployed area. Once when we restart the application server, the new files are getting overwritten with the old one. Is there any setting with which we can stop the weblogic server deploying the old war file again?

Hi,
I am stopping and restarting the weblogic server through startManagedWeblogic.sh script. I am not using the weblogic console. Some of our application developers directly drag and drop the Units in the Deployed Area for testing Purpose. Even with nostage mode the war file in the upload folder is getting redeployed at the time of server restart.

How so we schedule a reports server restart

We want to schedule a reports server restart each night that is scheduled in windows. Does anyone know the command to do this?
The reason we want to do this is because our RDF reports often error out and a simple restart of the reports server solves the issue. Has anyone else encountered this issue and if so how did you get round it?

Hi
This is really a reports question. You can auto schedule with the queue manager to run reports on the 27th of the month in background, or have a batch script to initiate them or write a new report that initiates each ot the reports so that it can be user initiated
Brian

Web Service from stateful Session Bean deleted after server restart

Hi,
i created a stateful session bean and from this a web service.
I am able to deploy it and it works really fine.
My problem is: after a server restart the web service is gone and i
have to deploy it again.
I have some other web services (but these are web services from stateless session beans)
but they "survive" the server restart.
I don't want to deploy the web service after every server restart, did I forget something or
is it a general problem of stateful session beans or web services?
Thanks in advance
Jens

Hello Björn,
I am not quite sure what your problem is but did you have a look at these articles:
http://help.sap.com/saphelp_nw04/helpdata/en/4d/993441c73cef23e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/be/2e2c4142aef623e10000000a155106/frameset.htm
I hope they can give you some idea.
Regads
Vyara

Missing data after server restart

Hi,
We restarted our MDM server at the OS level last night. Everything seemed okay after the restart. However, when our users came in this morning, they found that some data was missing from a table. We have a Material repository with 3 main tables. Some data which have previously been populated was not appearing in our Products Detail table, the largest of the three. A large number of rows in the table had columns that failed to load with data on the repository auto-start that occured after the server restart. The auto start value in the mds.ini file was set at 300 (5 minutes) as we had seen this iisue happen once before, and thought that may help.
A stop and restart of the repository corrected the issue. Is there anything we could have done to prevent this? Is it worthwhile to try increasing the auto start delay again? Validating detail data after every server restart is not an effective option.
MDM version: 7.1 SP08
OS: AIX DB: Oracle 11g
Thanks!
Dave

Hi Dave,
I meant that when you load repository using Immediate data is loaded from .acl files (accelerator files) in a async manner.
Whereas when you load by Update Indices new acl files are generated.
Below men6tioned is a comparision between the 2 ways of laoding repository:
Load Repository Immediate
o Loads indexes from accelerator files instead of being regenerated by reading the data them from the DB and creating the index.
o Automatically builds indexes stored in out-of-date accelerator files.
o Is usually fast.
 Load Repository with Update Indices
o Rebuilds all MDM indexes files by reading and indexing data stored in the DB. The results are flushed on disk as accelerator files.
o Necessary by repository schema changes or if any error occurs.
o Might take significant amount of time to complete.
So when you observe some visual data impact in your repository it is good idea to rebuild indexes.
I guess we cannot schedule this as default behavior is to load by immediate even through the inin parameter.
as a best practice one can do this by fixing a time frame eg monthly depending on data/schema changes.
Thanks,
Ravi

Best Practice to troubleshoot a Crawler Issue after SQL Server restarts

Hi Everyone
I am after some general advice or a suggested place to start when troubleshooting crawler issues after an unplanned, out-of-sequence server restart.
Specifically, the SQL Database in the SharePoint 2010 farm. Better yet, is there a standard practice way of resolving such issues?<o:p></o:p>
So far articles I have found suggest options from reviewing the crawl logs, creating a new crawl component, right through to using fiddler to monitor the crawler.
Are these sufficient places to start / methodologies to follow, what else should be considered?
Any advice greatly appreciated.
Thanks,
Mike

Well, as I said before, there are lots of different potential issues & resolutions for crawlers. It really depends on the issue. I would say that the base troubleshooting steps start the same no matter which service/feature you are looking
at. So, I'll try to keep this sort of generic, but beyond finding the details of the problem, the SOP or process will vary greatly based on what the error is. I hope this helps, and sorry if it's not specific enough.
1 - check the ULS logs
2 - check the windows application logs
3 - verify related services are running (get-spserviceinstance), possibly stop/start them to reprovision the instance on the affected server
4 - clear the config cache (this alone will clear about 30% of your basic problems)
6 - verify disk space & resource consumption on affected server (& SQL, SQL is always the potential to be the true "affected" server)
7 - iisreset
8 - verify connectivity between all servers in the farm and SP
9 - verify requir3ed features activated
10- check if any changes were made to environment recently (new hardware, updates to OS or apps, updates to GPOs, new solutions, etc)
11- check if the issue is reproducible in another environment (only reliable if this is a similar environment, i.e. same patch level test farm or dr farm). see if it occurs in other site collections within the web app, different web apps, different
servers/browsers, etc, basically just try to nail down the scope of the problem
There is a whole slew of thiings you could check from verifying certificates & perms, to rerunning psconfig, to checking registry keys, again I go back to it depends. hopefully this can get you started though. in the end ULS is where all
the real info on the issue is going to be, so make sure you check there. don't go in with tunnel vision either. if you see other errors in ULS, check them out, they may or may not be related; SharePoint is an intricate product with way more moving
parts than most systems. fix the little quick ones that you know you can handle, this will help to keep the farm clean and healthy, as well as crossing them off the list of potential suspects for your root cause.
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

Composites in "Unknown" state after managed soa server restart

Hi,
I am using SOA suite 11.1.1.6 version on 64 bit OEL Linux. I am getting following error in managed server output log files:
Feb 20, 2013 5:59:32 AM IST> <Error> <oracle.integration.platform> <SOA-20003> <Unable to register service.
oracle.fabric.common.FabricException: Error in getting XML input stream: oramds:/deployed-composites/WirelessEnterprise/svcEnrichSEARequest_rev1.0/svcEnrichSEARequest.wsdl: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/deployed-composites/WirelessEnterprise/svcEnrichSEARequest_rev1.0/svcEnrichSEARequest.wsdl does not exist.
Though this composites gets loaded, the composites dependent on this composite goes into "Unknown" state. Other composites are properly loaded on server restart.
Please let us know if anybody has any solution to this problem.

Hi,
Thanks for your help.
we have narrowed down to problem now.
The actual problem occurs while redeploying same composite on same revision.
E.g 3 composites A, B and C are deployed on and in "Up" state.
B And C composites depends on A.
B composite composite.xml has following entry
<import namespace="http://xmlns.oracle.com/A"
location="oramds:/deployed-composites/Enterprise/A_rev1.0/A.wsdl"
importType="wsdl"/>
same entry exist for C composite.xml as well.
Now whenever composite A is redeployed with same revision (1.0 in our case), and managed servers are restarted, B and C composites goes in to "Unknown" state.
Moving A.wsdl to /apps/wsdl/* in MDS works but it duplicates the A.wsdl file beacause it also exists in MDS @ /deployed-composites/Enterprise/A_rev1.0/A.wsdl
Please let us know if anyone has any solution.
Thanks,
Rupesh.

OSB Server restart

Similar Messages

Maybe you are looking for