16 Working with JD Edwards EnterpriseOne OMW and SCM Integration

This chapter contains the following topics:

• Section 16.1, "Configuring JD Edwards EnterpriseOne OMW and SCM Integration"

• Section 16.2, "Understanding the SCM Tool"

16.1 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.

16.1.1 Configuring JD Edwards EnterpriseOne OMW to Interface with ClearCase

Access the Object Management Configuration form.

1. Click the Configure Source Management Integration button.

2. On the Source Management Setup form, select the Enable JD Edwards EnterpriseOne OMW/SCM Integration check box to enable JD Edwards EnterpriseOne OMW/SCM integration, or clear the check box to disable JD Edwards EnterpriseOne OMW/SCM integration.

3. If you have opted to enable JD Edwards EnterpriseOne OMW/SCM integration, select the following object types that you want to integrate between the applications:

   • Applications

   • Batch Applications

   • Business Function

   • Data Structure

   • Tables

   • Business Views

4. In the Choose the source code management software to integrate with field, select ClearCase.

5. Select or clear the Enable backup on delete check box. If you select check box, the system renames and moves an object's text components when the object is deleted from an ERP pathcode. If you clear the check box, the system removes an object's text components from the folder location that is associated to the ERP pathcode from which the object was deleted. This folder resides on the SCM server.

6. Click OK.

16.1.2 Configuring Access to ClearCase

When JD Edwards EnterpriseOne OMW interfaces with ClearCase, it uses a "view" to decipher what in ClearCase a user is allowed to access. This view has rules associated to it that enable or restrict users' access to certain objects. For example, you might want one set of users to have access only to application objects; another set of users to have access to business view objects. Therefore, you can have many views and many users to whom you want to assign the same view. Instead of manually assigning the same set of rules to a view for each user, you can create a view profile that contains a set of rules that are automatically assigned to a view each time the view is used, eliminating you from having to manually assign the rules to each view for each user accessing it.

You must complete the Access Configuration process before you can complete the Pathcode Configuration process.

Access the Object Management Configuration form.

1. Click the Access Configuration button.

   You must complete the Access Configuration before you can continue to the Pathcode Configuration.

2. On the Work with Source Management Access form, click the Add button to add a new SCM view, or click the Find button, and click a view from the list.

   If you want to add an access configuration, continue to step 4. If you choose an existing access configuration, go to step 6.

3. Click Add.

4. In the View field, enter a view name.

5. In the View Profile field, enter the path and directory where the view profile you want to use resides in Clear Case.

   JD Edwards EnterpriseOne OMW will validate that this is a valid and accessible path to a view profile.

6. Click OK.

7. Click Close.

16.1.3 Configuring Pathcodes

In JD Edwards EnterpriseOne OMW, when a user saves, checks in, or transfers an object, the object's specifications are placed in the pathcode that has been assigned to the object. This pathcode is specified by the transfer activity rules. Because of the integration of JD Edwards EnterpriseOne OMW and ClearCase, when a user saves, checks in, or transfers an object, a .txt file is generated that contains information on the object. This file must be placed in a directory located in ClearCase. When you configure a pathcode, you define the location in which JD Edwards EnterpriseOne OMW will place the .txt. file in ClearCase.

The .txt files that are generated are dependent upon the file type that are assigned to the object. There are several different file types, each containing its own set of information. These file types are already assigned by default to the object. The following table lists the file types associated with each object:

Object Type	File Type
NER ER	ER — Event Rule Printout NH — NER Business Function Header NS — NER Business Function Source
C BSFN	BH — C Business Function Header BS — C Business Function Source
APPL	ER — Event Rule DH — Data Structure Header
UBE	ER — Event Rule DH — Data Structure Header
TABLE	TH — Table Header
BSVW	VH — View Header
DSTR	DH — Data Structure Header
NA	BF — Backup Folder
NA	DF — Default

When you configure a pathcode, you define in what folder the .txt files that are generated for each file type will reside. For example, you might want all .txt files that are generated for objects with the ER file type associated with them to reside in an ER folder.

Access the Object Management Configuration form.

1. Click the Path Configuration button.

2. On the Source Management Pathcode Configuration form, click the Add button.

3. In the Path Code field, enter the pathcode and directory in Clear Case where you want the generated .txt files to be placed.

   You can also click the Visual Assist button and select a pathcode from the list.

   Note:

   If the directory does not exist, select the Create Folder check box to have JD Edwards EnterpriseOne OMW create the folder.

4. In the EnterpriseOne File Type field, enter a file type.

   JD Edwards EnterpriseOne OMW uses this file type to sort the .txt files into the appropriate folders in Clear Case. For example, all ER .txt files will be placed in the one folder you entered or chose in step 3. Oracle recommends that you always assign the Default file type to at least one pathcode. The Default folder is the location where the .txt files will be placed should you fail to assign a pathcode to a file type.

16.1.4 Setting up a Backup Folder for Deleted Objects

You can ensure that the .txt files that are generated when a user deletes an object are saved to a folder upon deletion. To do so, configure a pathcode record where the file type is BF.

16.1.5 Copying a Path Code

You can copy the information associated with a pathcode. This ability enables you to quickly and easily create records for a new pathcode without having to manually associate information to it that already exists for another pathcode.

Access the Work With Source Management Pathcode Configuration form.

1. Click the Find button to retrieve existing pathcodes.

2. Click the pathcode you want to copy, and then click the Copy Pathcode row exit.

3. On the Copy Source Management Pathcode Configuration form, enter the new pathcode in the To Path Code field.

   You can also click the Visual Assist button and choose an existing pathcode.

4. Click OK.

16.2 Understanding the SCM Tool

The SCM tool is an interface that enables ERP developers to access all of the archival information collected on JD Edwards EnterpriseOne OMW objects. The SCM tool displays the version history information collected by JD Edwards EnterpriseOne OMW and enables ERP developers to find details about how one version of a text component differs from another version. The SCM tool is secure and contains functionality that is tailored for ERP developers to view version history information created by the integration with SCM.

You access the SCM tool through JD Edwards EnterpriseOne OMW.

16.2.1 SCM Interface and Functionality

The SCM tool contains panes from which you select objects and view information about them. Two of the panes are browsers from which you can select objects to view information about the objects. The other parts of the interface display the information about the objects you selected.

16.2.2 Source and Target Browsers

The Source and Target browsers contain tree structures. The tree contains a folder and file structure of either the SCM server to which the tool is currently connected, or the file and folder structure of the local machine on which you are working. Which folder and file structure the browsers display is dependent on the Server tab located at the bottom of each browser you select. When you select a file or folder, the field located at the top of the browsers is populated with the full path to that selected file or folder. You can also manually enter a path into the field if you know the path in which a file or folder is located.

See "Button and Icons".

The Source and Target browsers contain three node types. The following table shows the node icons, the node type, and contains a description of the icon:

Icon	Node Type	Description
	File	Represents a file.
	No Access	Represents anything in the storage structure to which the current user does not have permissions to access.
	Folder	Represents a folder.

16.2.3 History, Source History and Target History, Label Contents Viewers

To the right of the browsers are the following four tabs:

• History

• Source History

• Target History

• Label Contents

16.2.3.1 History Tab

The History tab consists of two tables that display information about the folder or file selected in the Source or Target browsers. When you select a folder or file that resides on an SCM server in either browser, the version history for that folder or file displays in the corresponding History viewer. For each version, the viewer displays the version number (this is the version number assigned the version by the SCM server), the SCM user that checked the version in, the time the version was checked in, the date the version was checked in, and the comment the version with which the version was checked in. On top of the table is a text field that indicates the SCM file for which the history is displayed. The same is true respectively for the target history viewer and the target file browser.

16.2.3.2 Source History and Target History Tabs

When you select a file in the Source browser, and when you select a revision of the file in the Source History viewer and press the Visual Assist button, the SCM tool displays the contents of the selected file in the Source Viewer tab. The same is true for the for the Target File viewer; when you select a file in the Target browser, and when you selected a revision of the file in the Target History viewer, the SCM tool displays the contents of the selected file in the Source Viewer tab. Two text fields reside on top of the file contents pane: the File and the Revision fields. The File field displays the pathname and name of the SCM file that you selected. The lower text field displays the version of the file that you selected.

Both the Source Viewer and Target History tabs are divided into two panes: the top displays the selected file's contents, the bottom contains a text field you use to search for specific lines of text within the content. After the SCM tool finds the specific text, it displays the text in the bottom pane. You can enter any literal string.

The SCM tool clears any content loaded in either the Source Viewer or the Target Viewer tabs when you select a different file or folder in the respective browsers.

16.2.3.3 Labeling Viewer

If the SCM with which JD Edwards EnterpriseOne OMW is integrated supports revision labeling functionality, the SCM tool displays a Label Contents tab, which contains the Label Contents viewer. When you select an SCM folder node in either the Source or Target browser, the SCM tool displays the label information for the folder or file selected. At the top of the Label Contents viewer is the Path field. This field displays the folder path that is currently selected in the SCM if the folder is at a level that contains revision labels. Directly below the Path field are two edit fields: From and To. When you click the Search button next to these fields, the SCM tool will search for all labels that exist for the SCM folder specified in the Path text field. The system displays all labels that are found as a node in the tree underneath the Search button. The To and From edit fields are filters for the Search button. If you enter a value in the From edit field, the SCM tool displays only those labels that have names greater than the value in the From field. If you enter a value in the To field, the SCM tool displays only those labels that have names that are less than the value in the To field.

An exception to the explanation listed above is if the To and From values are the same, in which case, the SCM tool displays only the label that has a name that matches the To and From field.

16.2.3.4 Button and Icons

The following table displays the icons and buttons in the SCM tool, and describes their functionality.

Icon	Name	Action Menu Item (Hot Key)	Enabled	Function
	Get	Get (Ctrl + G)	When you select an SCM server file in the source file browser and a local client folder in the target file browser.	Loads a copy of the revision of the file you selected in the source file browser and moves it to the folder selected in the target file browser.
	Compare	Compare (Ctrl + Z)	When you select any file in the source file browser and you select a file with the same file extension in the target file browser.	Loads the configured file comparison tool to compare the following files: the selected revision of the file in the source file browser to the selected revision of the file in the target file browser.
	Merge	Merge (Ctrl + M)	When you select any file in the source file browser and a local client file with the same file extension in the target file browser.	Loads the configured file merge tool to compare the differences between the selected revision of the file selected in the source file browser to the file selected in the target file browser, then allow the developer to merge those differences into the file selected in the target file browser.
	Get Label	Get Label Files (Ctrl + L)	When at least one file is selected in the label contents viewer and a local client folder is selected in the target file browser.	Brings a copy of the specific revision of the selected files that are attached to the selected revision label down to the local client folder selected in the target file browser.

16.2.4 Using the SCM Tool

Access JD Edwards EnterpriseOne OMW.

1. From JD Edwards EnterpriseOne OMW, click the Form exit, and then click SCM Tool.

2. On Source Code Management Tool, click the folder containing the contents you want to view or modify, and then click an object.

3. Click the appropriate tab to view the associated information.