WebSphere traditional and Liberty bindings files are used to provide information to bind the deployment information specified in the application to a specific resource. For example, it might map a logical name of an external resource to the actual physical JNDI name of the resource. For additional information see Application bindings in the WebSphere Application Server documentation.

WebSphere traditional and Liberty extension files contain additions to the standard descriptors for Java Platform, Enterprise Edition (Java EE) applications.

During migration, information that maps to WebSphere traditional and Liberty bindings and extensions files is moved from the WebLogic and JBoss deployment descriptors so that it is available to the WebSphere Application Server. If the file does not exist, one is created.

The following bindings and extension files are created for different project types:

File Type	File name
J2EE 1.4 and lower
EJB module bindings	META-INF/ibm-ejb-jar-bnd.xmi
EJB module extensions	META-INF/ibm-ejb-jar-ext.xmi
Web module bindings	WEB-INF/ibm-web-bnd.xmi
Web extensions	WEB-INF/ibm-web-ext.xmi
Java EE 5 and higher
EJB module bindings	META-INF/ibm-ejb-jar-bnd.xml
EJB module extensions	META-INF/ibm-ejb-jar-ext.xml
Web module bindings	WEB-INF/ibm-web-bnd.xml
Web extensions	WEB-INF/ibm-web-ext.xml

In Liberty, Application bindings can be added to the application configuration in the server.xml.