OSB File Transport and Path Service Error Solution

Problem

In a disaster recovery scenario, when a managed server that is configured as the primary node for the file transport-based proxy service goes down, due to some technical issue, then the file will go into error folder and hamper the processing of all the file transport-based services.           

Solution

1. Login to OSB Console (sbconsole) with weblogic credentials
2. Create a Session
3. Go to each file transport-based proxy service and change the Managed Server to OSB Managed server which is in up and running state
4. Save all your changes and Activate the session
5. Login to Weblogic Admin Console with weblogic credentials
6. Go to Path Services
7. Click on OSBFileTransportPathService
8. Go to Targets tab and change the targets to the OSB managed server which is in up and running state. NOTE: Please choose same OSB managed server name in step 3 and 8
9. Now, reprocess all the failed file/s