Configuring CA View DRAS to work with stand-alone transformers

Products

• Deliver
• Output Management Web Viewer

Issue/Introduction

Configuring CA View, DRAS to work with stand-alone transformers for use with Web Viewer

After reviewing:

CA DRAS and CA Spool Java Transformers

CA Spool Java Transformers

I will need some additional help as there are a lot of concepts/ background related to CA-VIEW that need an explanation.

Environment

Release : 12.2, 14.0

Component : CA Distributed Repository Access System (CA DRAS)

CA Spool

Web Viewer

CA View

Resolution

1. Review all parameters of the DRAS started task related to the Transformers. Read about installation and customization in the CA Spool Java Transformers documentation.

   
   Start the Java Transformers
   
   Customizing Java Transformers
   
   
   
2. The Java Transformers started task requires a complete OMVS segment including an UID, HOME and PGM attributes. The requirements are the same as the CA Spool started task. The documentation reference is:
   
   Implement Security
   
   Regarding security of the Java Transformer task, the permissions of the documentation are for CA Spool but they are the same for the Java Transformer started task. As long as the userid has a complete OMVS segment you can use the same userid for CADRAS and the ESFD2EB started tasks.
   
   
3. Apply all published maintenance for the Java Transformers

Additional Information

You are not required to use the directories specified in the JCL provided by SO12579 ADD ESFSMFRP - SMF METRICS REPORTING UTILITY (NEW FEATURE) which adds JCL to create the optional Java Transforms USS directories.   But here are some reasons why you may want to use them:

• These are the directories that are updated during the Transformers usage, that is, files are created and deleted from those folders during report transformation. So, you may want to keep them separated from the original directories created by the Transformers installation.
• In particular, the /apps directory is the place where you may have your customized transformation parameter files. if you use the /apps installation directory you may lose your customizations when you apply maintenance (PTFs)
• The /input and /output folders are the ones that may require additional space as depending on the size of the reports being transformed you may need more space in the zFS dataset than originally allocated during the installation.
  Again, keeping the directories in a separate, bigger zFS dataset may be a good idea.