WCS | EJB files to be committed in repository | Steps to take care in Server Env

Steps to be taken care while working with Access Beans in WCS:

Step 1:

After creating/updating Access Beans in local environment, only the following files has to be committed in repository,

Java Files:
1. WebSphereCommerceServerExtensionsData\ejbModule\com\abc\member\objects\XLogKey.java
2. WebSphereCommerceServerExtensionsData\ejbModule\com\abc\member\objects3. \XLogHome.java
3. WebSphereCommerceServerExtensionsData\ejbModule\com\abc\member\objects\XLogFactory.java
4. WebSphereCommerceServerExtensionsData\ejbModule\com\abc\member\objects\XLogBean.java
5. WebSphereCommerceServerExtensionsData\ejbModule\com\abc\member\objects\XLogAccessBeanData.java
6. WebSphereCommerceServerExtensionsData\ejbModule\com\abc\member\objects\XLogAccessBean.java
7. WebSphereCommerceServerExtensionsData\ejbModule\com\abc\member\objects\XLog.java

Configuration Files:
1. WebSphereCommerceServerExtensionsData\ejbModule\META-INF\backends\DB2UDBNT_V95_1\Map.mapxmi
2. WebSphereCommerceServerExtensionsData\ejbModule\META-INF\backends\DB2UDBNT_V95_1\ProfileDBSchema.dbm
3. WebSphereCommerceServerExtensionsData\ejbModule\META-INF\ejb-jar.xml
4. WebSphereCommerceServerExtensionsData\ejbModule\META-INF\ibm-ejb-access-bean.xmi
5. WebSphereCommerceServerExtensionsData\ejbModule\META-INF\ibm-ejb-jar-bnd.xmi
6. WebSphereCommerceServerExtensionsData\ejbModule\META-INF\ibm-ejb-jar-ext.xmi

Step 2:

While moving to next higher environment the data source has to be updated to point to that appropriate database in ibm-ejb-jar-bnd.xmi,

If your data source of the environment is "MyDBSource" then defaultCMPConnectionFactory's JNDI should look like the following,

<?xml version="1.0" encoding="UTF-8"?>
<ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:ejb="ejb.xmi" xmlns:ejbbnd="ejbbnd.xmi" xmi:id="EJBJarBinding_1041304850140" currentBackendId="DB2UDBNT_V95_1">
.......
.......
  <defaultCMPConnectionFactory xmi:id="CMPConnectionFactoryBinding_1069893248765" jndiName="jdbc/WebSphere Commerce DB2 DataSource MyDBSource" resAuth="Per_Connection_Factory"/>
</ejbbnd:EJBJarBinding>

Step 3:

Go to Server's Administration Console and update JNDI name 

Applications --> Application Types --> WebSphere enterprise applications --> WC_<SERVERENV> --> Enterprise Java Bean Properties --> Provide default data source mapping for modules containing 1.x entity beans

Update Target Resource JNDI Name in the appropriate input box,

jdbc/WebSphere Commerce DB2 DataSource MyDBSource