Web Services › How Access to a Data Source Works

How Access to a Data Source Works

Web Services is delivered as an AXIS2 archive file (EndevorService.aar). Tomcat automatically or manually deploys this .aar file. The EndevorService component (also known as a web service end point) has a lifecycle in that it can be started and ended. During the initialization phase, the EndevorService component scans the webapps/endevor folder and identifies and validates the configuration files (*.cfg) that it finds. If a validation failure occurs, the configuration file is discarded. To add, delete, or modify a .cfg file, the EndevorService.aar component must be stopped and restarted.

The client application or the Eclipse-Based UI connection wizard can access a list of validated data sources. The list includes the description, status, and message extracted from the configuration file. The EndevorService.aar file receives the SOAP envelope from the client. This SOAP message from the client application includes a dataSource parameter in the LoginProperities object. This parameter indicates the data source (CA Endevor SCM instance) that the client application wants to access.

A client can have access to more than one validated data source at the same time.

• There can be more than one valid configuration file in the webapps/endevor folder. For example, A1.cfg, A2.cfg, B1.cfg, and B2.cfg could access data sources named: A1, A2, B1, and B2.
• Different configuration files could specify the same started task on the same or on a different CAICCI host. The name of the .cfg file must match the name of the data source specified by the Name value in the .cfg file. However, the name of the data source does not need to be the same as the started task JobName value specified in the .cfg file.

  For example, in the following table, each *.cfg file accesses a data source using the started task on the host computer. All three of these data sources could be available at the same time.