Cleaning up old OSB Proxy Services

OSB old proxy services still lingering around in deployments:

Sometimes even if you delete a Proxy Service, the deployment remains in the console:
C:\Oracle2\Middleware\user_projects\domains\osb_domain\sbgen\_ALSB_1314101342219.ear

even if the ear file doesn't exist;
in config.xml you find:

<app-deployment>
    <name>_ALSB_1314101342219</name>
    <target>myCluster</target>
    <module-type>ear</module-type>
    <source-path>sbgen\_ALSB_1314101342219.ear</source-path>
    <sub-deployment>
      <name>ejb.jar</name>
      <target>myCluster</target>
    </sub-deployment>
    <plan-dir>osb\config\plan</plan-dir>
    <plan-path>Plan-_ALSB_1314101342219.ear.xml</plan-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
  </app-deployment>

workaround: just delete the entry from config.xml.

you should also remove the associated plan:

C:\Oracle2\Middleware\user_projects\domains\osb_domain\osb\config\plan\Plan-_ALSB_1314101342219.ear.xml

anyway all those EARs are normally deployed with staging-mode=stage (the case above is an exception), so you should check also in the DOMAIN_HOME/servers/SERVERNAME/stage folder. See also http://docs.oracle.com/cd/E23943_01/web.1111/e13702/deploy.htm#i1027041

The Administration Server first copies the deployment unit source files to the staging directories of target servers. (The staging directory is named stage by default, and it resides under the target server's root directory.) The target servers then deploy using their local copy of the deployment files.