Verifying the Installation and Configuration in Enterprise Developer

Use the following procedure for verifying the installation and configuration process based on a defined Enterprise Sync connection which synchronizes Endevor elements with AccuRev files. The following must be installed and configured before continuing this procedure:

Enterprise Sync
The installation must be complete and configured successfully for the synchronization process. The synchronization process should be running. See Enterprise Sync Server Configuration.
Enterprise Developer
The installation must be complete and the AccuRev Eclipse Plugin as well as the AWM AccuRev Integration Plugin must be installed on top of Enterprise Developer
Workflow Manager (AWM) Endevor Attachment
The installation must be complete and configured successfully.
AccuRev Client
The AccuRev client must be installed on the same machine where the Enterprise Developer is installed
  1. Start Enterprise Developer.
  2. On the Workspace Launcher dialog box, enter a workspace name of your choice. Then click OK.
  3. If this is the first time you start Enterprise Developer, you are presented with the Eclipse Welcome page. Click Open Team Developer Perspective to close the Welcome page and open the Team Developer Perspective. If the Welcome page is not opened, click Window > Open Perspective > Other, select the Team Developer (default) and click OK.
  4. Click the Remote Systems tab.
  5. Create a remote system (mainframe) connection (if a connection to your mainframe has not been pre-configured and is therefore not listed):
    1. On the Remote Systems tab, click .
    2. Select Micro Focus z/Server, then click Next.
    3. Enter the details of the mainframe that has z/Server and MFA server installed.
      Important: Enter exactly the same host name which has been used when configuring the Endevor data source on the Enterprise Sync server.
    4. Click Next, enter the MFA port number for the installation on the mainframe, and edit the host code pages, as required, and then click Finish.
      Note: It should be the same port and the same session code page which has been used when configuring the Endevor data source on the Enterprise Sync server.
  6. Connect to your mainframe system with your mainframe credentials.
  7. The mainframe connection was successful if the background color of the icons is displayed in green. Verify your Enterprise Developer mainframe installation (Mainframe Access Server and z/Server installation) and the network connectivity, if the connection cannot be established.
  8. The Application Explorer view should display a mainframe system entry after the mainframe connection has been established. If the system entry is not visible select, Add system(s)… from the context menu and select the previously created mainframe system. If this mainframe system entry is still not visible, then verify that the z/Server User server configuration and that the Workflow Manager Endevor Attachment has been correctly configured.
  9. When expanding the mainframe system entry in the Application Explorer view, an application with the name Enterprise Sync V2.2 Endevor Application should be visible. Select Load Application from the context menu.

    If this application entry is not visible, then verify that the Workflow Manager Endevor Attachment has been correctly configured and the application has been added correctly to the Workflow Manager's Master Configuration file.

    Note: The application name might be different in your installation.
  10. Expand the Endevor entry a few times until Endevor elements are listed in the tree view. If this doesn't work, verify that the Workflow Manager Endevor Attachment has been correctly installed and configured and the z/Server user server has access to the Endevor installation.
  11. On the AccuRev Workspace entry select New > Project … from the context menu.
  12. In the New Project wizard, select AccuRev>Project from AccuRev and click Next. If this project is not visible, verify that the AccuRev Eclipse plugin has been correctly installed on top of Enterprise Developer.
  13. Select the AccuRev server address and port (port 5050 is default). Then select the AccuRev depot and a gated stream which you want to use as a basis for creating an AccuRev workspace. You may have to login to AccuRev first. Then click Next. If no depot is visible or no streams are displayed verify the following:
    1. Verify that your AccuRev login credentials were correct (logout/login).
    2. Verify that an AccuRev depot exists on the server.
    3. Verify that the stream structure has been defined in this AccuRev depot including the required gated streams.
  14. Enter the AccuRev Workspace Name. This could be the same name as the parent stream, because AccuRev will add your user name automatically. Specify a path on your disk outside the Eclipse workspace (e.g. c:\microfocus\esd\) and then click Next.
  15. Enter an Eclipse Project Name and then click Next.
  16. Create the workspace in a General Eclipse Project. Then click Next and then Finish to create the AccuRev workspace in a general Eclipse project.
  17. Refresh the workspace entry in the Application Explorer view.
  18. Expand the workspace a few times and navigate to a folder where you would expect the synchronized Endevor elements. Select one COBOL file any verify that the Properties view contains values for the AccuRev and Endevor properties. This means that the Endevor metadata have been correctly synchronized to AccuRev.

    If you don't see the folder structure when expanding the stream, verify that the Enterprise Sync server has been configured correctly and that the initial synchronization has been executed.

    If the properties view doesn't contain AccuRev and Endevor metadata verify that the AWM AccuRev integration plugin has been installed on top of Enterprise Developer.

  19. Verify that the AccuRev WebUI works by selecting Team > WebUI from the context menu.
  20. The WebUI window should open. Click on the Stream Browser which should display the stream structure. If the WebUI window doesn't open verify that the AccuRev server's settings.xml file has been created correctly and the AccuRev Web Service is running.