You can add files accessible on a client machine to CA Endevor SCM and retrieve elements from CA Endevor SCM. Web Services transfers files to and from the client application using SOAP attachments. To enable the translation of transferred data, a CA Endevor SCM Type record must be properly defined for each type of data to be managed. The characteristics of binary and text files are described next:
CA Endevor SCM defines a text file as one that has line delimiters and requires character translation. You can store text files on the mainframe and browse them in CA Endevor SCM. Detailed change history is stored for text files.
Browsing an element in CA Endevor SCM invokes the EBCDIC-to-ASCII conversion function of CA Endevor SCM; the EBCDIC-to-local file system encoding is not used. However, when you retrieve a text file from CA Endevor SCM, the Web Services server converts EBCDIC from the mainframe.
Important: The CA Endevor SCM administrator must work with the web services administrator to properly define the element Type for text files.
The CodePage Web Services parameter in the Web Services configuration file defines the character sets for the mainframe and Web Services. The configuration file is customized by your Web Services administrator. A description of this parameter follows:
Specifies the code page, defined in the mainframe operating system, that CA Endevor SCM is using. The code page is a variation of the Extended Binary Coded Decimal Interchange Code (EBCDIC) that defines how text files are coded on the mainframe.
The CodePage and CharacterSet parameters enable Web Services to translate the plain text information exchanged between the client computer and the API. Plain text information includes SCL commands sent to the API and reports and CSV files extracted from the API.
For information about supported encodings, see: http://download.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html
Default: cp01140
Note: For more information about the configuration file parameters, see ENDEVOR.cfg Parameters.
CA Endevor SCM defines a binary file as one that does not have line delimiters or require character translation. Examples of binary files are Microsoft Word documents or Excel spreadsheets. Long names are typically used for naming binary files. Specific file versions can be retrieved through Web Services. You can browse binary files whose content type is recognized by your browser when using Web Services. Detailed change history is stored for binary files, except for file Types defined with log delta format. For more information about binary files, see How to Define an Element Type for Binary Files.
|
Copyright © 2013 CA.
All rights reserved.
|
|