If you have a custom ODA and you modify its start script but the message files include a prefix, the ODA may not start with Adapter Framework 2.6. The procedure below describes how to complete the migration by fixing this problem.
To enable a custom ODA with prefixed message files to start with Adapter Framework 2.6, do the following:
<?xml version="1.0" encoding="utf-8" ?> - <oda> - <startup> <messagefile prefix="<prefix_>" /> </startup> </oda>
where the values of the prefix_ attribute specifies the prefix.