Configuring JD Edwards EnterpriseOne OMW and SCM Integration

JD Edwards EnterpriseOne OMW enables you to integrate with third-party Source Control Management (SCM). SCM applications store objects that you create in JD Edwards EnterpriseOne OMW and create new versions of an object each time you check it in. Since older versions are saved, you can refer back to them to review changes. This is especially useful in determining at what point in the development process errors might have compromised an object.

Your ability to integrate with an SCM from JD Edwards EnterpriseOne OMW depends on whether the functionality that provides the integration is turned on or off. You can decide which JD Edwards EnterpriseOne OMW objects you want integrated in an SCM. For example, you might want to enable integration for report and business function objects while leaving table, business view, and data structure objects untouched.

This table shows the objects to manage, along with the components for which versions are created.

Metadata Object	Components on which an SCM application creates versions
BSFN	The source (.c) and header (.h) files of both C and NER business function objects. For NER business functions, an JD Edwards EnterpriseOne OMW will create a readable event rules printout.
TBLE	The header (.h) file.
BSVW	The header (.h) file.
DSTR	A generated text file containing the type definition of the data structure object.
APPL	A generated text file containing an application level printout of the event rules contained in the application.
UBE	A generated text file containing an application level printout of the event rules contained in the batch application.