If you get the following errors:

CWSXM0202E: An unexpected exception occurred when processing mediation flow for component MM_xServiceV1_Specific in module MM_xServiceV1_Specific:
CWSXM1025E: An unexpected exception occurred when the flow was called:
CWSXM0111E: Service runtime exception calling an import from mediation component MM_xServiceV1_Specific in module MM_xServiceV1_Specific:
CWSXM0204E: A configuration error occurred when calling a mediation flow.: Unexpected RuntimeException caught in prepareFaultSMO. An error occurred while parsing native data: The error message is: java.io.IOException: Error reading XML.
Caused By: java.io.IOException: Error reading XML

Your WSDL doesn’t match with the service WSDL. Check the name of areas in request and response of the service in your WSDL file.

After “Clean” process, if you lose MessageFilter’s matching codes that is located in the response of Specific Mediation, you should change your workspace. Firstly; create a new workspace, copy your project into new one and use new workspace.

Error:
Publishing failed
deployFailure
Deploying MM_XServiceV1_SpecificEJB
Deployment from com.ibm.ws.sca.runtime.core.deployer.SCAJ2EEDeployer had errors:
RMIC was interrupted by the following: null.

Solution:
To solve this problem you should change your workspace.
Firstly; create a new workspace, copy your project into new one and use new workspace.

If you find following error in logs:
“org.omg.CORBA.OBJECT_NOT_EXIST: SERVANT_NOT_FOUND (4) for key XXX vmcid: IBM minor code: C14 completed: No”
it means that connected SCA module could not be initiated or installed.

Solution:
Check the accuracy of all connected SCA modules’ installations, starting statuses and SCA binding properties.

For example:
If you have a line similar to the following sysout log:

CNTR0092W: Attempted to access EnterpriseBean MM_OperationsServiceV2x3_SpecificApp#MM_OperationsServiceV2x3_SpecificEJB.jar#export.Exp_OperationsServiceV2x3_Specific_SCA, that has not been started.

This shows us mentioned backend mediation is in stopped status.

Take a project interchange of the service mediation and library projects and use them. Do NOT perform these operations on code in clearcase.

Refactoring the Mediation Module
In Busıness Integration view:
-right click on the mediation project, refactor its name to reflect the new service version.
-under the mediation project > Integration Logic > Mediation Flows refactor the mediation flow implementation to reflect the new service version.
In the Assembly Diagram:
-refactor the mediation component name to reflect the new service version.
-click on an empty location, go to Properties view and click “Repair Name”, to fix the name of the mediation module.
Close/Open the mediation project at this point if the builder gives any error like ConcurrentModificationException.

Refactoring the Interface Library
We will first refactor the old library to the new service version and then drop this library and replace it with the real library. This trick saves us from hundreds of string replacements in mediation implementation files.
In Busıness Integration view:
-right click on the library project, refactor its name to reflect the new service version.
-under Web Service Ports refactor the service namespace to reflect the new service version.
-under Interfaces refactor the service namespace and name of the interface to reflect the new service version.
-under Data Types right click on one of the input output data types and refactor its namespace to reflect the new service version. Accept if the IDE warns you about other types that will also be affected.

Replace the library with the desired one
-Delete the refactored library project from workspace. It is not needed anymore.
-Import the new library project.

Error:
1GERR000:ResourceException thrown in J2CMethodBindingImpl.invoke() com.ibm.connector2.ims.ico.IMSDFSMessageException: ICO0079E: com.ibm.connector2.ims.ico.IMSTCPIPManagedConnection@197a197a.getOutputData(InteractionSpec) error. IMS returned a DFS message:
DFS2533 12:16:52 ROUTING CODE NOT ACTIVE
Solution:
When you get “ROUTING CODE NOT ACTIVE” message, we should understand that IMS Region is closed.

Error:
soapenv:Server.generalException
com.ibm.websphere.sca.ServiceRuntimeException:
CWSXM0201E: Exception returned by mediation flow for component MM_XXServiceV1 in module MM_XXServiceV1_Jet: Unexpected RuntimeException caught in prepareFaultSMO. An error occurred while parsing native data: The error message is: java.io.IOException: Error reading XML.
Caused By: java.io.IOException: Error reading XML: caused by: com.ibm.wsspi.sibx.mediation.MediationConfigurationException: Unexpected RuntimeException caught in prepareFaultSMO. An error occurred while parsing native data: The error message is: java.io.IOException: Error reading XML.
Caused By: java.io.IOException: Error reading XML

Solution:
“v1:approvingId” name is not compliance with WSDL name.

Error:
CWSCA9091E: The wsExports > wsExport [XXServiceV1x0_SIT_Gateway_WebService_Port1] specified in the custom deployment settings could not be found. ibm-deploy.scaj2ee XXServiceV1_Jet Unknown SCDL Validation Marker

Solution:
There is no XXV1x0_SIT_Gateway_WebService_Port1 WSDL file in the library.