An Overview for CA Output Management Web Viewer (OMWV/DVWeb), CA Output Management Document Viewer (DVPC) and CA Cooperative Processing.

book

Article ID: 53131

calendar_today

Updated On:

Products

CA Output Management Document Viewer CA Output Management Web Viewer

Issue/Introduction

Description

How do all these pieces fit together? Which components perform what functions? How does all of this work? Perhaps the best way to answer these commonly asked questions, is to trace the activity or flow that is generated as the result of an end-user request. So let's start there - with an end-user bringing up their browser and pointing to their OMWV Web Server.

Solution

<Please see attached file for image>

Figure 1

The process begins when the user starts their browser and points to their home page for the CA OMWV Server (index.htm). The browser will establish a connection, through IIS - Microsoft's Web Services utility. IIS allows web sites to exist on MS Windows-based (Win/XP, Win/2003, Win2008) machines. From the initial web page, the user clicks a link to access the Output Management Web Viewer sign on. It is at this point that the user begins interfacing with the Web Viewer and its components. On of the components is MS-SQL which can reside on the same server as does CA OMWV. But, it may also be installed on another server that is accessible from the CA OMWV server. The point is that the SQL DocView Web database is accessed to determine if the UserID is defined and which report folders are available. This SQL DVWeb database information is defined and maintained from the OMWV Admin Tool, and reflects what the Distributed Repository Access System (DRAS) knows about the repositories on the mainframe.

Next, the MS Windows-based machine will communicate via TCP/IP and CCI/PC-ENF with DRAS on the Mainframe. DRAS knows which report repositories are available and how they relate to the folder views that were set up back in the AdminTool on the OMWV server. It's this view of what's stored in CA View, CA Dispatch and/or CA Bundl, through whichever filters the user has employed, that is transmitted back through the above configuration all the way to the user's web browser. That's how the user winds up viewing the report list and ultimately, the report they wanted to see.

You can add additional layers of complexity, security and flexibility by adding additional mainframes/LPARs and report repositories? even additional products like CA CCI TCP Gateway, CCI/SSL and CA Output Management Document Viewer (OMDV/DVPC) to the above diagram, making it look more like the expanded diagram below.

<Please see attached file for image>

Figure 2

Environment

Release:
Component: DVPC

Attachments

1558721074498000053131_sktwi1f5rjvs16vw0.gif get_app
1558721072360000053131_sktwi1f5rjvs16vvz.gif get_app