Developer Guide: Difference between revisions
From Sysgem Support
Jump to navigationJump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! | Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! | ||
This guide | This guide outlines the concepts for developing and/or customizing SEM modules. It introduces the SEM Framework and the tools for developing, testing, and releasing software for the SEM environment. | ||
Readers of this guide should have a prior understanding of the programming language [http://en.wikipedia.org/wiki/Perl Perl] for developing scripts to run on the Windows platform and optionally the command languages for the following platforms: | Readers of this guide should have a prior understanding of the programming language [http://en.wikipedia.org/wiki/Perl Perl] for developing scripts to run on the Windows platform and optionally the command languages for the following platforms: | ||
* UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell]) | * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell]) | ||
* OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL]) | * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL]) | ||
| Line 16: | Line 16: | ||
== Overview: SEM Components == | == Overview: SEM Components == | ||
An overview of the | An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page. | ||
It describes the purpose of the following software components that are installed with the Sysgem Enterprise Manager and it gives an overview of how the components interact with each other: | |||
* | * SEM Authorization Server | ||
* | * SEM Management Console (GUI) | ||
* SEM Agents | |||
== Developer Examples == | == Developer Examples == | ||
Below is a list of | Below is a list of topics giving tips and programming examples to help the SEM Developer: | ||
* [[Dialogue Boxes]] | * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.) | ||
* [[AUTO_APPLY]] command. (Do not pause to gather input after making a menu selection, but action the transaction as soon as the menu option is selected.) | |||
* [[AUTO_CLOSE]] command. (Automatically close the input form after a transaction is complete.) | |||
* [[APPLY_OFF]] command. (Do not allow the transaction to proceed. The "Apply" button on the input form is made unavailable. The only option is to cancel the transaction after reading the error message.) | |||
Latest revision as of 16:06, 21 January 2011
The SEM Development Guide
Welcome to the Sysgem Enterprise Manager (SEM) Development Guide!
This guide outlines the concepts for developing and/or customizing SEM modules. It introduces the SEM Framework and the tools for developing, testing, and releasing software for the SEM environment.
Readers of this guide should have a prior understanding of the programming language Perl for developing scripts to run on the Windows platform and optionally the command languages for the following platforms:
- Linux / UNIX (Korn Shell)
- OpenVMS (DCL)
- OS/400 (CL)
Overview: SEM Components
An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the SEM Overview page.
It describes the purpose of the following software components that are installed with the Sysgem Enterprise Manager and it gives an overview of how the components interact with each other:
- SEM Authorization Server
- SEM Management Console (GUI)
- SEM Agents
Developer Examples
Below is a list of topics giving tips and programming examples to help the SEM Developer:
- Dialogue Boxes. (Display Information/warning/error messages in a pop-up box.)
- AUTO_APPLY command. (Do not pause to gather input after making a menu selection, but action the transaction as soon as the menu option is selected.)
- AUTO_CLOSE command. (Automatically close the input form after a transaction is complete.)
- APPLY_OFF command. (Do not allow the transaction to proceed. The "Apply" button on the input form is made unavailable. The only option is to cancel the transaction after reading the error message.)
