Customizing CARMA using plug-in projects tutorial
CARMA can be customized by using Eclipse plug-in projects. The following modules provide you with a starting point in developing your own CARMA customization.
Note: Module 1-5 and 9 are independent of each other and
can be completed in any order. Modules 6-8 build off of Module 5 and
each other, as a result they must be completed in order. Module 9
involves some host configuration of the Sample PDS RAM, which might
involve special permissions.
Learning objectives
After completing the modules in this module, you will have an understanding of the following concepts:- Creating an Developer for z/OS® Eclipse plug-in project
- Using the plug-in Manifest Editor to add dependencies and extensions
- Use the
plugin.xmlfile to modify extensions and their attributes - Create packages, classes, and folders within an Eclipse plug-in project
- Create and modify Java™ classes to add enhanced functionality to the plug-ins
Time required
The time that is required to complete these modules vary. Each module contains an approximate time required.Prerequisites
To successfully complete the modules, you should have:- Developer for z/OS installed on your local workspace
- Access to a z/OS host system and any required authentication
- Basic understanding of Java coding and debugging
Tip:
Eclipse plug-in development requires the Plug-in
Development perspective. This perspective is not enabled by default in Developer for z/OS. To enable it:
- Open the Preferences window.
- Navigate to .
- On the Capabilities page, expand Development and select Plug-in Development.
- Click Apply and Close.
- Module 1: Adding decorators to the user interface
This module takes you through the steps to add a decorator, or image overlay, to the CARMA members shown in the CARMA Repositories view. - Module 2: Hide or disable CARMA actions with plug-in extension points
There are several ways to develop CARMA plug-ins. This module explores hiding and disabling CARMA actions using plug-in extension points. - Module 3: Disable CARMA actions programmatically
This module guides you through how to hide or disable CARMA actions programmatically. The result of this module is the same as Module 2. - Module 4: Adding an action to CARMA menu using plug-in extension points
In this module, you create a Browse Member Action, and add it to the CARMA menu using an extension point. This new action allows for aCARMAMemberto be selected and opened in a read-only mode. - Module 5: Creating a new CARMA view using the existing CARMA context provider
This module will take you through the steps of creating a new CARMA view using the default CARMA context provider. - Module 6: Creating and using a custom label provider to customize a view
This module guides you through the steps of creating and using a custom label provider to customize the CARMA view you created in Module 5. - Module 7: Creating a new view using a custom context provider
This module takes you through the steps of creating and using a custom context provider to customize a CARMA view. TheContextProvider, which you create, controls how the context of the CARMA model is displayed in the view. This module demonstrates how to customize the context provider to filter out repository instances that are PDS part of the build process (that is, the listing, object, and load PDS). It will also only show PDS that are associated with CARMA, the PDS that have a CARMA token in the name. - Module 8: Creating a custom menu for a custom view
This module teaches you how to create a custom menu for a custom view. - Module 9: Introduction to parameter and action extension points
This module explores the capabilities of CARMA extension points in providing customization to parameters and actions that are associated with a custom action on a particular RAM.