Sysgem Support - User contributions [en]

https://wiki.sysgem.com/api.php?action=feedcontributions&feedformat=atom&user=Mike.schofield Sysgem Support - User contributions [en] 2026-07-05T06:08:20Z User contributions MediaWiki 1.44.0 https://wiki.sysgem.com/index.php?title=Change_Input_Field_View&diff=378 Change Input Field View 2012-07-23T11:30:04Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Finding your way around the SEM development Interface''<br /> <br /> <br /> '''Dynamically Changing Fields in a SEM Input Form from the "Fields" script'''<br /> <br /> The purpose of the "Fields" script is to populate an input form before it is displayed, but not only can the text within a field be changed, but the characteristics of the field can also be changed.<br /> <br /> This section describes the possibilities for changing the input form from the Fields script before the form is displayed.<br /> <br /> '''Adding Text into a Field''' <br /> <br /> print "AA : text data\n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Making a Field Read-Only'''<br /> <br /> print "AA ! \n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Making a Field Read-Write'''<br /> <br /> print "AA ~ \n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Hiding a Field'''<br /> <br /> print "AA - \n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Setting a List of Selectable Entries in a List Field'''<br /> <br /> print "AA @ 1st entry\\2nd entry\\3rd entry\n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Adding Selectable Entries to an Existing Set in a List Field'''<br /> <br /> print "AA + 4th entry\\5th entry\\6th entry\n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Pre-Selecting Entries in a List Field'''<br /> <br /> print "AA : 2nd entry,5th entry\n"; # where "AA" is the field code of the required field {on a List(multi-select) field} <br /> <br /> <br /> '''Making a Field an 'Optional' Field'''<br /> <br /> Making a field an optional field puts a checkbox infront of the field which has to be selected to make the field active.<br /> <br /> print "AA ? \n"; # where "AA" is the field code of the required field</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=File:LogErrorTab.jpg&diff=376 File:LogErrorTab.jpg 2011-06-09T14:52:53Z

<p>Mike.schofield: </p> <hr /> <div></div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Error_Tab_of_Log_Window&diff=375 Error Tab of Log Window 2011-06-09T14:51:38Z

<p>Mike.schofield: Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. ---- ''How to make an entry in the Error tab of the Log Window:'' '''Error Tab Log Messa..."</p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''How to make an entry in the Error tab of the Log Window:''<br /> <br /> <br /> '''Error Tab Log Messages'''<br /> <br /> Send the following output from a script, e.g. from a Windows script:<br /> <br /> print "\@{{ON\n";<br /> print "this is the error message\n";<br /> print "\@{{ERROR\n";<br /> print "\@{{OFF\n";<br /> <br /> This produces an entry in the Error tab of the log window as follows:<br /> <br /> [[FILE:LogErrorTab.jpg]]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=SEM_Development_Guide&diff=374 SEM Development Guide 2011-06-09T11:48:38Z

<p>Mike.schofield: </p> <hr /> <div>== Introduction to the SEM Development Guide ==<br /> <br /> Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! <br /> <br /> 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. <br /> <br /> 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:<br /> <br /> * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell])<br /> <br /> * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL])<br /> <br /> * OS/400 ([http://en.wikipedia.org/wiki/AS/400_Control_Language CL])<br /> <br /> <br /> == Overview of SEM Components ==<br /> <br /> This section 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:<br /> <br /> * SEM Authorization Server<br /> <br /> * SEM Management Console (GUI)<br /> <br /> * SEM Agents<br /> <br /> An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page.<br /> <br /> <br /> == Start the SEM Development Interface ==<br /> <br /> This section describes how to edit either your own private SEM library or a SEM Module library that is available to all users of the SEM system.<br /> <br /> Before you can access the SEM Development Interface the following three conditions need to be satisfied:<br /> <br /> * Your SEM License has to contain the permission to use the Development Interface<br /> <br /> * The SEM 'Master Profile' on your system needs to have the permission set<br /> <br /> * The SEM 'User Profile' allocated to your SEM account needs to have the permission set<br /> <br /> To learn how to set up and start the SEM Development Interface please read the [[Start SEM Development Interface]] page.<br /> <br /> <br /> == Navigate the SEM Development Interface ==<br /> <br /> This section describes the features available to the SEM Developer and how to navigate around a SEM library.<br /> <br /> The first display shown after selecting the "Edit" ( [[File:DevBlueHammer.jpg]] ) option is a list of "Custom Display Windows" that are contained within the library.<br /> <br /> Editing a Custom Display gives the following 'property' pages<br /> <br /> * General Page<br /> <br /> * Startup Page<br /> <br /> * Service Display Page<br /> <br /> * Data Cache Page<br /> <br /> * Columns Page<br /> <br /> * Layouts Page<br /> <br /> * Common Page<br /> <br /> * Menu Page<br /> <br /> * Drag and Drop Page<br /> <br /> * Scripts Page<br /> <br /> To learn how to create or customize Windows and options within a SEM Module using the SEM Development Interface please read the [[Navigate SEM Development Interface]] page.<br /> <br /> <br /> == SEM User Permissions ==<br /> <br /> A user needs an Account in Sysgem Enterprise Manager (SEM) in order to use the product. A SEM user account needs an "Access Control Profile" to control the level of 'SEM Base Privileges', and an Access Control Profile needs "Access Control Token(s)" to control the level of privileges offered by SEM Module(s).<br /> <br /> The following sections describe how SEM Accounts, Profiles and Tokens are set up and how the settings are accessed by scripts:<br /> <br /> * [[SEM User Accounts]] (How to set up a SEM User Account)<br /> <br /> * [[Access Control Profiles]] (Access Control Profiles are allocated to a 'SEM User' to control what 'SEM Base Privileges' are available)<br /> <br /> * [[Access Control Tokens]] (Access Control Tokens are allocated to a 'Profile' to control what 'SEM Module Privileges' are available)<br /> <br /> <br /> == Developer Examples ==<br /> <br /> Below is a list of topics giving tips and programming examples to help the SEM Developer:<br /> <br /> <br /> '''''Defining the Characteristics of an Input Form:'''''<br /> <br /> * [[Field Definitions]]. (How to create and set up the permanent characteristics of fields on a SEM input form using the SEM Development Interface.)<br /> <br /> * [[Change Input Field View]]. (How to dynamically change the view of fields on a SEM input form from the "Fields" script.)<br /> <br /> <br /> '''''Input Variables Preset in Scripts by the SEM Framework:'''''<br /> <br /> * [[Script Input Variables]]. (Script variables preset by the SEM framework before a script is run and then available as input to the script.)<br /> <br /> <br /> '''''Controlling Subsequent Actions After a Script has Run:'''''<br /> <br /> * [[Start-up Initialization]]. (Setting Values in the Start-up window of a SEM Display)<br /> <br /> * [[Suppress Agent Output in Post-process]]. (Normal output from the SEM Agent may be intercepted and modified by Post-processing) <br /> <br /> * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.)<br /> <br /> * [[Error Tab of Log Window]]. (Adding an entry into the Error pane of the Log Window.)<br /> <br /> * [[AUTOAPPLY]] command. (Do not pause to gather input after making a menu selection, but action the transaction as soon as the menu option is selected.)<br /> <br /> * [[AUTOCLOSE]] command. (Automatically close the input form after a transaction is complete.)<br /> <br /> * [[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.)<br /> <br /> <br /> '''''Passing Data to a Main Target Agent Script'''''<br /> <br /> * [[Main Display Pre-Processing Script Output]] (Passing data to the main target agent script when a SEM display is started)<br /> <br /> * [[ADD_SVR from a menu Pre-Process]] (Passing data to the main target agent script when a SEM Menu Option is run)<br /> <br /> <br /> <br /> '''''Retrieving Data from the Central Options Cache'''''<br /> <br /> * [[Fetch From Options Cache]] (Fetching data from the Authorization Server Options Cache)<br /> <br /> <br /> <br /> '''''Starting a 'Child' Window from a menu option on a 'Parent' Window'''''<br /> <br /> * [[Spawning a Child Window]] (Spawn a child window and pass data for display from the parent)</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=AUTOCLOSE&diff=373 AUTOCLOSE 2011-05-19T12:08:29Z

<p>Mike.schofield: Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. ---- ''How to automatically close the input form after a transaction is complete.'' '''A..."</p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''How to automatically close the input form after a transaction is complete.''<br /> <br /> <br /> '''AUTO_CLOSE'''<br /> <br /> Normally, the "results pane" remains open after a SEM transaction is compleet, to show the output from the script that has run on the target system. Sometimes, however, it is desirable to close the window automatically as soon as the script has completed on the target server.<br /> <br /> Output the following string to standard output from any of the following scripts:<br /> <br /> * (M) Fields<br /> <br /> * (M) Pre-processing<br /> <br /> * (M) Post-processing<br /> <br /> * (M) AS400<br /> <br /> * (M) Windows / NT<br /> <br /> * (M) UNIX<br /> <br /> * (M) VMS<br /> <br /> <br /> '''String to output:'''<br /> <br /> "@{{AUTO_CLOSE"<br /> <br /> <br /> '''From a Perl script:''' <br /> <br /> print "\@{{AUTO_CLOSE\n";<br /> <br /> <br /> '''From a Korn Shell script:''' <br /> <br /> echo "@{{AUTO_CLOSE"<br /> <br /> <br /> '''From a DCL Shell script:''' <br /> <br /> $ write sys$output "@{{AUTO_CLOSE"</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=SEM_Development_Guide&diff=372 SEM Development Guide 2011-05-19T12:08:18Z

<p>Mike.schofield: </p> <hr /> <div>== Introduction to the SEM Development Guide ==<br /> <br /> Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! <br /> <br /> 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. <br /> <br /> 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:<br /> <br /> * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell])<br /> <br /> * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL])<br /> <br /> * OS/400 ([http://en.wikipedia.org/wiki/AS/400_Control_Language CL])<br /> <br /> <br /> == Overview of SEM Components ==<br /> <br /> This section 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:<br /> <br /> * SEM Authorization Server<br /> <br /> * SEM Management Console (GUI)<br /> <br /> * SEM Agents<br /> <br /> An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page.<br /> <br /> <br /> == Start the SEM Development Interface ==<br /> <br /> This section describes how to edit either your own private SEM library or a SEM Module library that is available to all users of the SEM system.<br /> <br /> Before you can access the SEM Development Interface the following three conditions need to be satisfied:<br /> <br /> * Your SEM License has to contain the permission to use the Development Interface<br /> <br /> * The SEM 'Master Profile' on your system needs to have the permission set<br /> <br /> * The SEM 'User Profile' allocated to your SEM account needs to have the permission set<br /> <br /> To learn how to set up and start the SEM Development Interface please read the [[Start SEM Development Interface]] page.<br /> <br /> <br /> == Navigate the SEM Development Interface ==<br /> <br /> This section describes the features available to the SEM Developer and how to navigate around a SEM library.<br /> <br /> The first display shown after selecting the "Edit" ( [[File:DevBlueHammer.jpg]] ) option is a list of "Custom Display Windows" that are contained within the library.<br /> <br /> Editing a Custom Display gives the following 'property' pages<br /> <br /> * General Page<br /> <br /> * Startup Page<br /> <br /> * Service Display Page<br /> <br /> * Data Cache Page<br /> <br /> * Columns Page<br /> <br /> * Layouts Page<br /> <br /> * Common Page<br /> <br /> * Menu Page<br /> <br /> * Drag and Drop Page<br /> <br /> * Scripts Page<br /> <br /> To learn how to create or customize Windows and options within a SEM Module using the SEM Development Interface please read the [[Navigate SEM Development Interface]] page.<br /> <br /> <br /> == SEM User Permissions ==<br /> <br /> A user needs an Account in Sysgem Enterprise Manager (SEM) in order to use the product. A SEM user account needs an "Access Control Profile" to control the level of 'SEM Base Privileges', and an Access Control Profile needs "Access Control Token(s)" to control the level of privileges offered by SEM Module(s).<br /> <br /> The following sections describe how SEM Accounts, Profiles and Tokens are set up and how the settings are accessed by scripts:<br /> <br /> * [[SEM User Accounts]] (How to set up a SEM User Account)<br /> <br /> * [[Access Control Profiles]] (Access Control Profiles are allocated to a 'SEM User' to control what 'SEM Base Privileges' are available)<br /> <br /> * [[Access Control Tokens]] (Access Control Tokens are allocated to a 'Profile' to control what 'SEM Module Privileges' are available)<br /> <br /> <br /> == Developer Examples ==<br /> <br /> Below is a list of topics giving tips and programming examples to help the SEM Developer:<br /> <br /> <br /> '''''Defining the Characteristics of an Input Form:'''''<br /> <br /> * [[Field Definitions]]. (How to create and set up the permanent characteristics of fields on a SEM input form using the SEM Development Interface.)<br /> <br /> * [[Change Input Field View]]. (How to dynamically change the view of fields on a SEM input form from the "Fields" script.)<br /> <br /> <br /> '''''Input Variables Preset in Scripts by the SEM Framework:'''''<br /> <br /> * [[Script Input Variables]]. (Script variables preset by the SEM framework before a script is run and then available as input to the script.)<br /> <br /> <br /> '''''Controlling Subsequent Actions After a Script has Run:'''''<br /> <br /> * [[Start-up Initialization]]. (Setting Values in the Start-up window of a SEM Display)<br /> <br /> * [[Suppress Agent Output in Post-process]]. (Normal output from the SEM Agent may be intercepted and modified by Post-processing) <br /> <br /> * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.)<br /> <br /> * [[AUTOAPPLY]] command. (Do not pause to gather input after making a menu selection, but action the transaction as soon as the menu option is selected.)<br /> <br /> * [[AUTOCLOSE]] command. (Automatically close the input form after a transaction is complete.)<br /> <br /> * [[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.)<br /> <br /> <br /> '''''Passing Data to a Main Target Agent Script'''''<br /> <br /> * [[Main Display Pre-Processing Script Output]] (Passing data to the main target agent script when a SEM display is started)<br /> <br /> * [[ADD_SVR from a menu Pre-Process]] (Passing data to the main target agent script when a SEM Menu Option is run)<br /> <br /> <br /> <br /> '''''Retrieving Data from the Central Options Cache'''''<br /> <br /> * [[Fetch From Options Cache]] (Fetching data from the Authorization Server Options Cache)<br /> <br /> <br /> <br /> '''''Starting a 'Child' Window from a menu option on a 'Parent' Window'''''<br /> <br /> * [[Spawning a Child Window]] (Spawn a child window and pass data for display from the parent)</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=SEM_Development_Guide&diff=371 SEM Development Guide 2011-05-19T12:07:22Z

<p>Mike.schofield: </p> <hr /> <div>== Introduction to the SEM Development Guide ==<br /> <br /> Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! <br /> <br /> 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. <br /> <br /> 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:<br /> <br /> * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell])<br /> <br /> * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL])<br /> <br /> * OS/400 ([http://en.wikipedia.org/wiki/AS/400_Control_Language CL])<br /> <br /> <br /> == Overview of SEM Components ==<br /> <br /> This section 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:<br /> <br /> * SEM Authorization Server<br /> <br /> * SEM Management Console (GUI)<br /> <br /> * SEM Agents<br /> <br /> An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page.<br /> <br /> <br /> == Start the SEM Development Interface ==<br /> <br /> This section describes how to edit either your own private SEM library or a SEM Module library that is available to all users of the SEM system.<br /> <br /> Before you can access the SEM Development Interface the following three conditions need to be satisfied:<br /> <br /> * Your SEM License has to contain the permission to use the Development Interface<br /> <br /> * The SEM 'Master Profile' on your system needs to have the permission set<br /> <br /> * The SEM 'User Profile' allocated to your SEM account needs to have the permission set<br /> <br /> To learn how to set up and start the SEM Development Interface please read the [[Start SEM Development Interface]] page.<br /> <br /> <br /> == Navigate the SEM Development Interface ==<br /> <br /> This section describes the features available to the SEM Developer and how to navigate around a SEM library.<br /> <br /> The first display shown after selecting the "Edit" ( [[File:DevBlueHammer.jpg]] ) option is a list of "Custom Display Windows" that are contained within the library.<br /> <br /> Editing a Custom Display gives the following 'property' pages<br /> <br /> * General Page<br /> <br /> * Startup Page<br /> <br /> * Service Display Page<br /> <br /> * Data Cache Page<br /> <br /> * Columns Page<br /> <br /> * Layouts Page<br /> <br /> * Common Page<br /> <br /> * Menu Page<br /> <br /> * Drag and Drop Page<br /> <br /> * Scripts Page<br /> <br /> To learn how to create or customize Windows and options within a SEM Module using the SEM Development Interface please read the [[Navigate SEM Development Interface]] page.<br /> <br /> <br /> == SEM User Permissions ==<br /> <br /> A user needs an Account in Sysgem Enterprise Manager (SEM) in order to use the product. A SEM user account needs an "Access Control Profile" to control the level of 'SEM Base Privileges', and an Access Control Profile needs "Access Control Token(s)" to control the level of privileges offered by SEM Module(s).<br /> <br /> The following sections describe how SEM Accounts, Profiles and Tokens are set up and how the settings are accessed by scripts:<br /> <br /> * [[SEM User Accounts]] (How to set up a SEM User Account)<br /> <br /> * [[Access Control Profiles]] (Access Control Profiles are allocated to a 'SEM User' to control what 'SEM Base Privileges' are available)<br /> <br /> * [[Access Control Tokens]] (Access Control Tokens are allocated to a 'Profile' to control what 'SEM Module Privileges' are available)<br /> <br /> <br /> == Developer Examples ==<br /> <br /> Below is a list of topics giving tips and programming examples to help the SEM Developer:<br /> <br /> <br /> '''''Defining the Characteristics of an Input Form:'''''<br /> <br /> * [[Field Definitions]]. (How to create and set up the permanent characteristics of fields on a SEM input form using the SEM Development Interface.)<br /> <br /> * [[Change Input Field View]]. (How to dynamically change the view of fields on a SEM input form from the "Fields" script.)<br /> <br /> <br /> '''''Input Variables Preset in Scripts by the SEM Framework:'''''<br /> <br /> * [[Script Input Variables]]. (Script variables preset by the SEM framework before a script is run and then available as input to the script.)<br /> <br /> <br /> '''''Controlling Subsequent Actions After a Script has Run:'''''<br /> <br /> * [[Start-up Initialization]]. (Setting Values in the Start-up window of a SEM Display)<br /> <br /> * [[Suppress Agent Output in Post-process]]. (Normal output from the SEM Agent may be intercepted and modified by Post-processing) <br /> <br /> * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.)<br /> <br /> * [[AUTOAPPLY]] command. (Do not pause to gather input after making a menu selection, but action the transaction as soon as the menu option is selected.)<br /> <br /> * [[AUTO_CLOSE]] command. (Automatically close the input form after a transaction is complete.)<br /> <br /> * [[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.)<br /> <br /> <br /> '''''Passing Data to a Main Target Agent Script'''''<br /> <br /> * [[Main Display Pre-Processing Script Output]] (Passing data to the main target agent script when a SEM display is started)<br /> <br /> * [[ADD_SVR from a menu Pre-Process]] (Passing data to the main target agent script when a SEM Menu Option is run)<br /> <br /> <br /> <br /> '''''Retrieving Data from the Central Options Cache'''''<br /> <br /> * [[Fetch From Options Cache]] (Fetching data from the Authorization Server Options Cache)<br /> <br /> <br /> <br /> '''''Starting a 'Child' Window from a menu option on a 'Parent' Window'''''<br /> <br /> * [[Spawning a Child Window]] (Spawn a child window and pass data for display from the parent)</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=AUTOAPPLY&diff=370 AUTOAPPLY 2011-05-19T12:06:58Z

<p>Mike.schofield: Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. ---- ''How to cause a transaction to be automatically started as soon as a menu option has..."</p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''How to cause a transaction to be automatically started as soon as a menu option has been selected.''<br /> <br /> <br /> '''AUTOAPPLY'''<br /> <br /> Normally, selecting a menu option will display a form and prompt the user for input before transmitting the transaction to the target agents. On some occasions, however, when there is no input data to be collected, it is desirable to proceed immediately into the transaction as soon as the menu option has been selected.<br /> <br /> Enter the following Perl statement in the "(M) Fields" script:<br /> <br /> print "\@{{AUTOAPPLY\n";</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=SEM_Development_Guide&diff=369 SEM Development Guide 2011-05-19T12:06:44Z

<p>Mike.schofield: </p> <hr /> <div>== Introduction to the SEM Development Guide ==<br /> <br /> Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! <br /> <br /> 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. <br /> <br /> 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:<br /> <br /> * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell])<br /> <br /> * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL])<br /> <br /> * OS/400 ([http://en.wikipedia.org/wiki/AS/400_Control_Language CL])<br /> <br /> <br /> == Overview of SEM Components ==<br /> <br /> This section 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:<br /> <br /> * SEM Authorization Server<br /> <br /> * SEM Management Console (GUI)<br /> <br /> * SEM Agents<br /> <br /> An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page.<br /> <br /> <br /> == Start the SEM Development Interface ==<br /> <br /> This section describes how to edit either your own private SEM library or a SEM Module library that is available to all users of the SEM system.<br /> <br /> Before you can access the SEM Development Interface the following three conditions need to be satisfied:<br /> <br /> * Your SEM License has to contain the permission to use the Development Interface<br /> <br /> * The SEM 'Master Profile' on your system needs to have the permission set<br /> <br /> * The SEM 'User Profile' allocated to your SEM account needs to have the permission set<br /> <br /> To learn how to set up and start the SEM Development Interface please read the [[Start SEM Development Interface]] page.<br /> <br /> <br /> == Navigate the SEM Development Interface ==<br /> <br /> This section describes the features available to the SEM Developer and how to navigate around a SEM library.<br /> <br /> The first display shown after selecting the "Edit" ( [[File:DevBlueHammer.jpg]] ) option is a list of "Custom Display Windows" that are contained within the library.<br /> <br /> Editing a Custom Display gives the following 'property' pages<br /> <br /> * General Page<br /> <br /> * Startup Page<br /> <br /> * Service Display Page<br /> <br /> * Data Cache Page<br /> <br /> * Columns Page<br /> <br /> * Layouts Page<br /> <br /> * Common Page<br /> <br /> * Menu Page<br /> <br /> * Drag and Drop Page<br /> <br /> * Scripts Page<br /> <br /> To learn how to create or customize Windows and options within a SEM Module using the SEM Development Interface please read the [[Navigate SEM Development Interface]] page.<br /> <br /> <br /> == SEM User Permissions ==<br /> <br /> A user needs an Account in Sysgem Enterprise Manager (SEM) in order to use the product. A SEM user account needs an "Access Control Profile" to control the level of 'SEM Base Privileges', and an Access Control Profile needs "Access Control Token(s)" to control the level of privileges offered by SEM Module(s).<br /> <br /> The following sections describe how SEM Accounts, Profiles and Tokens are set up and how the settings are accessed by scripts:<br /> <br /> * [[SEM User Accounts]] (How to set up a SEM User Account)<br /> <br /> * [[Access Control Profiles]] (Access Control Profiles are allocated to a 'SEM User' to control what 'SEM Base Privileges' are available)<br /> <br /> * [[Access Control Tokens]] (Access Control Tokens are allocated to a 'Profile' to control what 'SEM Module Privileges' are available)<br /> <br /> <br /> == Developer Examples ==<br /> <br /> Below is a list of topics giving tips and programming examples to help the SEM Developer:<br /> <br /> <br /> '''''Defining the Characteristics of an Input Form:'''''<br /> <br /> * [[Field Definitions]]. (How to create and set up the permanent characteristics of fields on a SEM input form using the SEM Development Interface.)<br /> <br /> * [[Change Input Field View]]. (How to dynamically change the view of fields on a SEM input form from the "Fields" script.)<br /> <br /> <br /> '''''Input Variables Preset in Scripts by the SEM Framework:'''''<br /> <br /> * [[Script Input Variables]]. (Script variables preset by the SEM framework before a script is run and then available as input to the script.)<br /> <br /> <br /> '''''Controlling Subsequent Actions After a Script has Run:'''''<br /> <br /> * [[Start-up Initialization]]. (Setting Values in the Start-up window of a SEM Display)<br /> <br /> * [[Suppress Agent Output in Post-process]]. (Normal output from the SEM Agent may be intercepted and modified by Post-processing) <br /> <br /> * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.)<br /> <br /> * [[AUTOAPPLY]] command. (Do not pause to gather input after making a menu selection, but action the transaction as soon as the menu option is selected.)<br /> <br /> * [[AUTOCLOSE]] command. (Automatically close the input form after a transaction is complete.)<br /> <br /> * [[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.)<br /> <br /> <br /> '''''Passing Data to a Main Target Agent Script'''''<br /> <br /> * [[Main Display Pre-Processing Script Output]] (Passing data to the main target agent script when a SEM display is started)<br /> <br /> * [[ADD_SVR from a menu Pre-Process]] (Passing data to the main target agent script when a SEM Menu Option is run)<br /> <br /> <br /> <br /> '''''Retrieving Data from the Central Options Cache'''''<br /> <br /> * [[Fetch From Options Cache]] (Fetching data from the Authorization Server Options Cache)<br /> <br /> <br /> <br /> '''''Starting a 'Child' Window from a menu option on a 'Parent' Window'''''<br /> <br /> * [[Spawning a Child Window]] (Spawn a child window and pass data for display from the parent)</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=SEM_Development_Guide&diff=368 SEM Development Guide 2011-05-19T12:06:01Z

<p>Mike.schofield: </p> <hr /> <div>== Introduction to the SEM Development Guide ==<br /> <br /> Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! <br /> <br /> 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. <br /> <br /> 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:<br /> <br /> * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell])<br /> <br /> * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL])<br /> <br /> * OS/400 ([http://en.wikipedia.org/wiki/AS/400_Control_Language CL])<br /> <br /> <br /> == Overview of SEM Components ==<br /> <br /> This section 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:<br /> <br /> * SEM Authorization Server<br /> <br /> * SEM Management Console (GUI)<br /> <br /> * SEM Agents<br /> <br /> An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page.<br /> <br /> <br /> == Start the SEM Development Interface ==<br /> <br /> This section describes how to edit either your own private SEM library or a SEM Module library that is available to all users of the SEM system.<br /> <br /> Before you can access the SEM Development Interface the following three conditions need to be satisfied:<br /> <br /> * Your SEM License has to contain the permission to use the Development Interface<br /> <br /> * The SEM 'Master Profile' on your system needs to have the permission set<br /> <br /> * The SEM 'User Profile' allocated to your SEM account needs to have the permission set<br /> <br /> To learn how to set up and start the SEM Development Interface please read the [[Start SEM Development Interface]] page.<br /> <br /> <br /> == Navigate the SEM Development Interface ==<br /> <br /> This section describes the features available to the SEM Developer and how to navigate around a SEM library.<br /> <br /> The first display shown after selecting the "Edit" ( [[File:DevBlueHammer.jpg]] ) option is a list of "Custom Display Windows" that are contained within the library.<br /> <br /> Editing a Custom Display gives the following 'property' pages<br /> <br /> * General Page<br /> <br /> * Startup Page<br /> <br /> * Service Display Page<br /> <br /> * Data Cache Page<br /> <br /> * Columns Page<br /> <br /> * Layouts Page<br /> <br /> * Common Page<br /> <br /> * Menu Page<br /> <br /> * Drag and Drop Page<br /> <br /> * Scripts Page<br /> <br /> To learn how to create or customize Windows and options within a SEM Module using the SEM Development Interface please read the [[Navigate SEM Development Interface]] page.<br /> <br /> <br /> == SEM User Permissions ==<br /> <br /> A user needs an Account in Sysgem Enterprise Manager (SEM) in order to use the product. A SEM user account needs an "Access Control Profile" to control the level of 'SEM Base Privileges', and an Access Control Profile needs "Access Control Token(s)" to control the level of privileges offered by SEM Module(s).<br /> <br /> The following sections describe how SEM Accounts, Profiles and Tokens are set up and how the settings are accessed by scripts:<br /> <br /> * [[SEM User Accounts]] (How to set up a SEM User Account)<br /> <br /> * [[Access Control Profiles]] (Access Control Profiles are allocated to a 'SEM User' to control what 'SEM Base Privileges' are available)<br /> <br /> * [[Access Control Tokens]] (Access Control Tokens are allocated to a 'Profile' to control what 'SEM Module Privileges' are available)<br /> <br /> <br /> == Developer Examples ==<br /> <br /> Below is a list of topics giving tips and programming examples to help the SEM Developer:<br /> <br /> <br /> '''''Defining the Characteristics of an Input Form:'''''<br /> <br /> * [[Field Definitions]]. (How to create and set up the permanent characteristics of fields on a SEM input form using the SEM Development Interface.)<br /> <br /> * [[Change Input Field View]]. (How to dynamically change the view of fields on a SEM input form from the "Fields" script.)<br /> <br /> <br /> '''''Input Variables Preset in Scripts by the SEM Framework:'''''<br /> <br /> * [[Script Input Variables]]. (Script variables preset by the SEM framework before a script is run and then available as input to the script.)<br /> <br /> <br /> '''''Controlling Subsequent Actions After a Script has Run:'''''<br /> <br /> * [[Start-up Initialization]]. (Setting Values in the Start-up window of a SEM Display)<br /> <br /> * [[Suppress Agent Output in Post-process]]. (Normal output from the SEM Agent may be intercepted and modified by Post-processing) <br /> <br /> * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.)<br /> <br /> * [[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.)<br /> <br /> * [[AUTOCLOSE]] command. (Automatically close the input form after a transaction is complete.)<br /> <br /> * [[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.)<br /> <br /> <br /> '''''Passing Data to a Main Target Agent Script'''''<br /> <br /> * [[Main Display Pre-Processing Script Output]] (Passing data to the main target agent script when a SEM display is started)<br /> <br /> * [[ADD_SVR from a menu Pre-Process]] (Passing data to the main target agent script when a SEM Menu Option is run)<br /> <br /> <br /> <br /> '''''Retrieving Data from the Central Options Cache'''''<br /> <br /> * [[Fetch From Options Cache]] (Fetching data from the Authorization Server Options Cache)<br /> <br /> <br /> <br /> '''''Starting a 'Child' Window from a menu option on a 'Parent' Window'''''<br /> <br /> * [[Spawning a Child Window]] (Spawn a child window and pass data for display from the parent)</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=SEM_Development_Guide&diff=367 SEM Development Guide 2011-05-19T12:05:25Z

<p>Mike.schofield: </p> <hr /> <div>== Introduction to the SEM Development Guide ==<br /> <br /> Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! <br /> <br /> 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. <br /> <br /> 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:<br /> <br /> * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell])<br /> <br /> * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL])<br /> <br /> * OS/400 ([http://en.wikipedia.org/wiki/AS/400_Control_Language CL])<br /> <br /> <br /> == Overview of SEM Components ==<br /> <br /> This section 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:<br /> <br /> * SEM Authorization Server<br /> <br /> * SEM Management Console (GUI)<br /> <br /> * SEM Agents<br /> <br /> An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page.<br /> <br /> <br /> == Start the SEM Development Interface ==<br /> <br /> This section describes how to edit either your own private SEM library or a SEM Module library that is available to all users of the SEM system.<br /> <br /> Before you can access the SEM Development Interface the following three conditions need to be satisfied:<br /> <br /> * Your SEM License has to contain the permission to use the Development Interface<br /> <br /> * The SEM 'Master Profile' on your system needs to have the permission set<br /> <br /> * The SEM 'User Profile' allocated to your SEM account needs to have the permission set<br /> <br /> To learn how to set up and start the SEM Development Interface please read the [[Start SEM Development Interface]] page.<br /> <br /> <br /> == Navigate the SEM Development Interface ==<br /> <br /> This section describes the features available to the SEM Developer and how to navigate around a SEM library.<br /> <br /> The first display shown after selecting the "Edit" ( [[File:DevBlueHammer.jpg]] ) option is a list of "Custom Display Windows" that are contained within the library.<br /> <br /> Editing a Custom Display gives the following 'property' pages<br /> <br /> * General Page<br /> <br /> * Startup Page<br /> <br /> * Service Display Page<br /> <br /> * Data Cache Page<br /> <br /> * Columns Page<br /> <br /> * Layouts Page<br /> <br /> * Common Page<br /> <br /> * Menu Page<br /> <br /> * Drag and Drop Page<br /> <br /> * Scripts Page<br /> <br /> To learn how to create or customize Windows and options within a SEM Module using the SEM Development Interface please read the [[Navigate SEM Development Interface]] page.<br /> <br /> <br /> == SEM User Permissions ==<br /> <br /> A user needs an Account in Sysgem Enterprise Manager (SEM) in order to use the product. A SEM user account needs an "Access Control Profile" to control the level of 'SEM Base Privileges', and an Access Control Profile needs "Access Control Token(s)" to control the level of privileges offered by SEM Module(s).<br /> <br /> The following sections describe how SEM Accounts, Profiles and Tokens are set up and how the settings are accessed by scripts:<br /> <br /> * [[SEM User Accounts]] (How to set up a SEM User Account)<br /> <br /> * [[Access Control Profiles]] (Access Control Profiles are allocated to a 'SEM User' to control what 'SEM Base Privileges' are available)<br /> <br /> * [[Access Control Tokens]] (Access Control Tokens are allocated to a 'Profile' to control what 'SEM Module Privileges' are available)<br /> <br /> <br /> == Developer Examples ==<br /> <br /> Below is a list of topics giving tips and programming examples to help the SEM Developer:<br /> <br /> <br /> '''''Defining the Characteristics of an Input Form:'''''<br /> <br /> * [[Field Definitions]]. (How to create and set up the permanent characteristics of fields on a SEM input form using the SEM Development Interface.)<br /> <br /> * [[Change Input Field View]]. (How to dynamically change the view of fields on a SEM input form from the "Fields" script.)<br /> <br /> <br /> '''''Input Variables Preset in Scripts by the SEM Framework:'''''<br /> <br /> * [[Script Input Variables]]. (Script variables preset by the SEM framework before a script is run and then available as input to the script.)<br /> <br /> <br /> '''''Controlling Subsequent Actions After a Script has Run:'''''<br /> <br /> * [[Start-up Initialization]]. (Setting Values in the Start-up window of a SEM Display)<br /> <br /> * [[Suppress Agent Output in Post-process]]. (Normal output from the SEM Agent may be intercepted and modified by Post-processing) <br /> <br /> * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.)<br /> <br /> * [[AUTOAPPLY]] command. (Do not pause to gather input after making a menu selection, but action the transaction as soon as the menu option is selected.)<br /> <br /> * [[AUTOCLOSE]] command. (Automatically close the input form after a transaction is complete.)<br /> <br /> * [[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.)<br /> <br /> <br /> '''''Passing Data to a Main Target Agent Script'''''<br /> <br /> * [[Main Display Pre-Processing Script Output]] (Passing data to the main target agent script when a SEM display is started)<br /> <br /> * [[ADD_SVR from a menu Pre-Process]] (Passing data to the main target agent script when a SEM Menu Option is run)<br /> <br /> <br /> <br /> '''''Retrieving Data from the Central Options Cache'''''<br /> <br /> * [[Fetch From Options Cache]] (Fetching data from the Authorization Server Options Cache)<br /> <br /> <br /> <br /> '''''Starting a 'Child' Window from a menu option on a 'Parent' Window'''''<br /> <br /> * [[Spawning a Child Window]] (Spawn a child window and pass data for display from the parent)</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=AUTO_APPLY&diff=366 AUTO APPLY 2011-05-19T12:04:37Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''How to cause a transaction to be automatically started as soon as a menu option has been selected.''<br /> <br /> <br /> '''AUTOAPPLY'''<br /> <br /> Normally, selecting a menu option will display a form and prompt the user for input before transmitting the transaction to the target agents. On some occasions, however, when there is no input data to be collected, it is desirable to proceed immediately into the transaction as soon as the menu option has been selected.<br /> <br /> Enter the following Perl statement in the "(M) Fields" script:<br /> <br /> print "\@{{AUTOAPPLY\n";</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Change_Input_Field_View&diff=365 Change Input Field View 2011-04-27T06:35:40Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Finding your way around the SEM development Interface''<br /> <br /> <br /> '''Dynamically Changing Fields in a SEM Input Form from the "Fields" script'''<br /> <br /> The purpose of the "Fields" script is to populate an input form before it is displayed, but not only can the text within a field be changed, but the characteristics of the field can also be changed.<br /> <br /> This section describes the possibilities for changing the input form from the Fields script before the form is displayed.<br /> <br /> '''Adding Text into a Field''' <br /> <br /> print "AA : text data\n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Making a Field Read-Only'''<br /> <br /> print "AA ! \n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Making a Field Read-Write'''<br /> <br /> print "AA ~ \n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Hiding a Field'''<br /> <br /> print "AA - \n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Setting a List of Selectable Entries in a List Field'''<br /> <br /> print "AA @ 1st entry\\2nd entry\\3rd entry\n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Adding Selectable Entries to an Existing Set in a List Field'''<br /> <br /> print "AA + 4th entry\\5th entry\\6th entry\n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Pre-Selecting Entries in a List Field'''<br /> <br /> print "AA : 2nd entry\\5th entry\n"; # where "AA" is the field code of the required field<br /> <br /> <br /> '''Making a Field an 'Optional' Field'''<br /> <br /> Making a field an optional field puts a checkbox infront of the field which has to be selected to make the field active.<br /> <br /> print "AA ? \n"; # where "AA" is the field code of the required field</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=364 Spawning a Child Window 2011-03-31T08:16:50Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> One window can be started from another window by:<br /> <br /> * adding code to the (M) Pre-processing script of menu option in the ''parent'' window<br /> * adding script comment in the Main Display Pre-processing script of the ''child'' window<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:<br /> <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.<br /> <br /> In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.<br /> <br /> In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. <br /> <br /> In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> The parent window can define which agents should be used when starting the child window. For example, the same agents are used by the child as are selected in entries on the parent window.<br /> <br /> There are three different ways of achieving this:<br /> <br /> 1. The parent determines the list of agents to be used by the child and the child window starts without any further prompting.<br /> <br /> 2. The parent determines the list of agents to be used by the child and the child window opens with the startup window that allows the user to accept or change the list of agents to be connected.<br /> <br /> 3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the list of agents is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.<br /> <br /> <br /> ''1. Automatically starting the child...''<br /> <br /> In the (M) Pre-processing script of the parent menu:<br /> <br /> <br /> <br /> #<br /> # Pass the server list to the child window<br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> foreach my $server (@servers)<br /> {<br /> print "\@{{START_DISPLAY_SERVER $server\n";<br /> }<br /> <br /> <br /> This will start the child window automatically and connect it to the selected servers.<br /> <br /> <br /> ''2. Starting the child display with suggested agents, and allowing the user to change the agent selection...''<br /> <br /> Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:<br /> <br /> In the Parent (M) Pre-processing script:<br /> <br /> <br /> #<br /> # Pass the server list to the child window <br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> print "\@{{START_DISPLAY_PARAM SV " . join("\,", @servers) . "\n";<br /> <br /> <br /> ... and in the startup initialize script of the child:<br /> <br /> <br /> <br /> #<br /> # set up the connect to agent list<br /> #<br /> <br /> print "\@{{LOAD_SERVERS $VALUE_SV\n"; # to preselect the same servers as those selected in the parent window<br /> <br /> <br /> <br /> ''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''<br /> <br /> <br /> ''3. Starting the child display with suggested agents, but not allowing the user to change the agent selection...''<br /> <br /> It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.<br /> <br /> To achieve this, the following script line should be added to the startup initialisation script after the print "\@{{LOAD_SERVERS command shown above.<br /> <br /> <br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used<br /> <br /> <br /> By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.<br /> <br /> ''(** Note: again, for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=362 Spawning a Child Window 2011-03-29T15:08:56Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> One window can be started from another window by:<br /> <br /> * adding code to the (M) Pre-processing script of menu option in the ''parent'' window<br /> * adding script comment in the Main Display Pre-processing script of the ''child'' window<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:<br /> <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.<br /> <br /> In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.<br /> <br /> In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. <br /> <br /> In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> The parent window can define which agents should be used when starting the child window. For example, the same agents are used by the child as are selected in entries on the parent window.<br /> <br /> There are three different ways of achieving this:<br /> <br /> 1. The parent determines the list of agents to be used by the child and the child window starts without any further prompting.<br /> <br /> 2. The parent determines the list of agents to be used by the child and the child window opens with the startup window that allows the user to accept or change the list of agents to be connected.<br /> <br /> 3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the list of agents is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.<br /> <br /> <br /> ''1. Automatically starting the child...''<br /> <br /> In the (M) Pre-processing script of the parent menu:<br /> <br /> <br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> foreach my $server (@servers)<br /> {<br /> print "\@{{START_DISPLAY_SERVER $server\n";<br /> }<br /> <br /> <br /> This will start the child window automatically and connect it to the selected servers.<br /> <br /> <br /> ''2. Starting the child display with suggested agents, and allowing the user to change the agent selection...''<br /> <br /> Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:<br /> <br /> In the Parent (M) Pre-processing script:<br /> <br /> <br /> #<br /> # Pass the server list to the child window <br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> ... and in the startup initialize script of the child:<br /> <br /> <br /> <br /> #<br /> # set up the connect to agent list<br /> #<br /> <br /> print "\@{{LOAD_SERVERS $VALUE_SV\n"; # to preselect the same servers as those selected in the parent window<br /> <br /> <br /> <br /> ''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''<br /> <br /> <br /> ''3. Starting the child display with suggested agents, but not allowing the user to change the agent selection...''<br /> <br /> It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.<br /> <br /> To achieve this, the following script line should be added to the startup initialisation script after the print "\@{{LOAD_SERVERS command shown above.<br /> <br /> <br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used<br /> <br /> <br /> By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.<br /> <br /> ''(** Note: again, for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=361 Spawning a Child Window 2011-03-29T15:05:03Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> One window can be started from another window by:<br /> <br /> * adding code to the (M) Pre-processing script of menu option in the ''parent'' window<br /> * adding script comment in the Main Display Pre-processing script of the ''child'' window<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:<br /> <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.<br /> <br /> In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.<br /> <br /> In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. <br /> <br /> In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> The parent window can define which agents should be used when starting the child window. For example, the same agents are used by the child as are selected in entries on the parent window.<br /> <br /> There are three different ways of achieving this:<br /> <br /> 1. The parent determines the list of agents to be used by the child and the child window starts without any further prompting.<br /> <br /> 2. The parent determines the list of agents to be used by the child and the child window opens with the startup window that allows the user to accept or change the list of agents to be connected.<br /> <br /> 3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the agent is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.<br /> <br /> <br /> ''1. Automatically starting the child...''<br /> <br /> In the (M) Pre-processing script of the parent menu:<br /> <br /> <br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> foreach my $server (@servers)<br /> {<br /> print "\@{{START_DISPLAY_SERVER $server\n";<br /> }<br /> <br /> <br /> This will start the child window automatically and connect it to the selected servers.<br /> <br /> <br /> ''2. Starting the child display with suggested agents, and allowing the user to change the agent selection...''<br /> <br /> Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:<br /> <br /> In the Parent (M) Pre-processing script:<br /> <br /> <br /> #<br /> # Pass the server list to the child window <br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> ... and in the startup initialize script of the child:<br /> <br /> <br /> <br /> #<br /> # set up the connect to agent list<br /> #<br /> <br /> print "\@{{LOAD_SERVERS $VALUE_SV\n"; # to preselect the same servers as those selected in the parent window<br /> <br /> <br /> <br /> ''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''<br /> <br /> <br /> ''3. Starting the child display with suggested agents, but not allowing the user to change the agent selection...''<br /> <br /> It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.<br /> <br /> To achieve this, the following script line should be added to the startup initialisation script after the print "\@{{LOAD_SERVERS command shown above.<br /> <br /> <br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used<br /> <br /> <br /> By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.<br /> <br /> ''(** Note: again, for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=360 Spawning a Child Window 2011-03-29T15:04:08Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> One window can be started from another window by:<br /> <br /> * adding code to the (M) Pre-processing script of menu option in the ''parent'' window<br /> * adding script comment in the Main Display Pre-processing script of the ''child'' window<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:<br /> <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.<br /> <br /> In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.<br /> <br /> In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. <br /> <br /> In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> The parent window can define which agents should be used when starting the child window. For example, the same agents are used by the child as are selected in entries on the parent window.<br /> <br /> There are three different ways of achieving this:<br /> <br /> 1. The parent determines the list of agents to be used by the child and the child window starts without any further prompting.<br /> <br /> 2. The parent determines the list of agents to be used by the child and the child window opens with the startup window that allows the user to accept or change the list of agents to be connected.<br /> <br /> 3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the agent is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.<br /> <br /> 1. Automatically starting the child...<br /> <br /> In the (M) Pre-processing script of the parent menu:<br /> <br /> <br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> foreach my $server (@servers)<br /> {<br /> print "\@{{START_DISPLAY_SERVER $server\n";<br /> }<br /> <br /> <br /> This will start the child window automatically and connect it to the selected servers.<br /> <br /> <br /> 2. Starting the child display with suggested agents, and allowing the user to change the agent selection...<br /> <br /> Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:<br /> <br /> In the Parent (M) Pre-processing script:<br /> <br /> <br /> #<br /> # Pass the server list to the child window <br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> ... and in the startup initialize script of the child:<br /> <br /> <br /> <br /> #<br /> # set up the connect to agent list<br /> #<br /> <br /> print "\@{{LOAD_SERVERS $VALUE_SV\n"; # to preselect the same servers as those selected in the parent window<br /> <br /> <br /> <br /> ''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''<br /> <br /> <br /> 3. Starting the child display with suggested agents, but not allowing the user to change the agent selection...<br /> <br /> It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.<br /> <br /> To achieve this, the following script line should be added to the startup initialisation script after the print "\@{{LOAD_SERVERS command shown above.<br /> <br /> <br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used<br /> <br /> <br /> By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.<br /> <br /> ''(** Note: again, for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=359 Spawning a Child Window 2011-03-29T14:48:18Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> One window can be started from another window by:<br /> <br /> * adding code to the (M) Pre-processing script of menu option in the ''parent'' window<br /> * adding script comment in the Main Display Pre-processing script of the ''child'' window<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:<br /> <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.<br /> <br /> In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.<br /> <br /> In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. <br /> <br /> In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> The parent window can define which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the parent: <br /> <br /> In the (M) Pre-processing script of the parent menu:<br /> <br /> <br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> foreach my $server (@servers)<br /> {<br /> print "\@{{START_DISPLAY_SERVER $server\n";<br /> }<br /> <br /> <br /> This will start the child window automatically and connect it to the selected servers.<br /> <br /> Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:<br /> <br /> In the Parent (M) Pre-processing script:<br /> <br /> <br /> #<br /> # Pass the server list to the child window <br /> #<br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> ... and in the startup initialize script of the child:<br /> <br /> <br /> <br /> #<br /> # set up the connect to agent list<br /> #<br /> <br /> print "\@{{LOAD_SERVERS $VALUE_SV\n"; # to preselect the same servers as those selected in the parent window<br /> <br /> <br /> <br /> ''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''<br /> <br /> <br /> It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.<br /> <br /> To achieve this, the following script line should be added to the startup initialisation script after the print "\@{{LOAD_SERVERS command shown above.<br /> <br /> <br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used<br /> <br /> <br /> By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=358 Spawning a Child Window 2011-03-29T09:29:27Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> One window can be started from a another window by:<br /> <br /> * adding code to the (M) Pre-processing script of menu option in the ''parent'' window<br /> * adding script comment in the Main Display Pre-processing script of the ''child'' window<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:<br /> <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.<br /> <br /> In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.<br /> <br /> In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. <br /> <br /> In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> The parent window can define which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the menu option of the parent and in the startip initialize script of the child:<br /> <br /> In the (M) Pre-processing script of the parent menu option:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> <br /> In the startup Initialize script of the child:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Open the selected server list from the parent window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> open(SVRS, "< $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> my @servers = <SVRS>;<br /> <br /> close(SRVS);<br /> <br /> print "\@{{LOAD_SERVERS $servers[0]\n"; # to preselect the same servers as those selected in the parent window<br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=357 Spawning a Child Window 2011-03-29T09:26:57Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> One window can be started from a another window by:<br /> <br /> * adding code to the (M) Pre-processing script of menu option in the ''parent'' window<br /> * adding script comment in the Main Display Pre-processing script of the ''child'' window<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:<br /> <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.<br /> <br /> In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.<br /> <br /> In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. <br /> <br /> In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> The parent window can define which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the menu option of the parent and in the startip initialize script of the child:<br /> <br /> In the (M) Pre-processing script of the parent menu option:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> <br /> In the startup Initialize script of the child:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Open the selected server list from the parent window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> open(SVRS, "< $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> my @servers = <SVRS>;<br /> <br /> close(SRVS);<br /> <br /> print "\@{{LOAD_SERVERS $servers[0]\n"; # to preselect the same servers as those selected in the parnet window<br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=356 Spawning a Child Window 2011-03-29T08:00:13Z

<p>Mike.schofield: </p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> To spawn a new window from a menu option, code needs to be entered in the '(M) Pre-processing script' of the menu option in the main 'Pre-processing' script of the child window.<br /> <br /> In the (M) Pre-processing script enter the following code: <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. The phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> <br /> The following code added to the Parent menu option (in the (M) Pre-processing script) will pass parameters to the child window using the selected entry in the parent window.<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Agent script of the child window when the display window has been spawned. In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> <br /> The parent window can specify which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the menu option of the parent and in the startip initialize script of the child:<br /> <br /> In the (M) Pre-processing script of the parent menu option:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> In the startup Initialize script of the child:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Open the selected server list from the parent window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> open(SVRS, "< $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> my @servers = <SVRS>;<br /> <br /> close(SRVS);<br /> <br /> print "\@{{LOAD_SERVERS $servers[0]\n"; # to preselect the same servers as those selected in the parnet window<br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Spawning_a_Child_Window&diff=355 Spawning a Child Window 2011-03-28T16:39:30Z

<p>Mike.schofield: Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. ---- ''Spawning a child window in SEM:'' '''To Initiate the Spawn Command from the Paren..."</p> <hr /> <div>'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.<br /> <br /> ----<br /> <br /> ''Spawning a child window in SEM:''<br /> <br /> <br /> '''To Initiate the Spawn Command from the Parent Window...'''<br /> <br /> To spawn a new window from a menu option, code needs to be entered in the '(M) Pre-processing script' of the menu option in the main 'Pre-processing' script of the child window.<br /> <br /> In the (M) Pre-processing script enter the following code: <br /> <br /> <br /> #<br /> # start another display window, passing along information<br /> # extracted from the selected entries.<br /> #<br /> # @{{START_DISPLAY_SCRIPT<br /> <br /> #<br /> # Don't display the menu dialog.<br /> #<br /> # @{{MENU_OPTION_SILENT <br /> #<br /> <br /> print "\@{{START_DISPLAY_TITLE Child Example\n";<br /> <br /> print "\@{{START_DISPLAY_NEW\n";<br /> <br /> print "\@{{START_DISPLAY_TILED\n";<br /> <br /> <br /> <br /> '''To Identify the Child Window...'''<br /> <br /> The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. The phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.<br /> <br /> <br /> #<br /> # @{{AUTOSTART_DISPLAY_TITLE Child Example<br /> #<br /> <br /> <br /> <br /> '''To Pass Parameters from the Parent to the Child Window...'''<br /> <br /> <br /> The following code added to the Parent menu option (in the (M) Pre-processing script) will pass parameters to the child window using the selected entry in the parent window.<br /> <br /> <br /> print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";<br /> print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";<br /> <br /> <br /> This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Agent script of the child window when the display window has been spawned. In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.<br /> <br /> <br /> '''To Determine which Agents Should be Started in the Child Window...'''<br /> <br /> <br /> The parent window can specify which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code neds to be added to the menu option of the parent and in the startip initialize script of the child:<br /> <br /> In the (M) Pre-processing script of the parent menu option:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Pass the server list to the child window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;<br /> <br /> open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> print SVRS join("\,", @servers) . "\n";<br /> <br /> close(SVRS);<br /> <br /> <br /> <br /> In the startup Initialize script of the child:<br /> <br /> <br /> use Sysgem;<br /> <br /> #<br /> # Open the selected server list from the parent window via a temporary file<br /> #<br /> my $path = "";<br /> <br /> Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);<br /> <br /> my $FilePath = $path . "\\Temp_SV_File.txt";<br /> <br /> open(SVRS, "< $FilePath") || die "Can't open $FilePath - $!\n";<br /> <br /> my @servers = <SVRS>;<br /> <br /> close(SRVS);<br /> <br /> print "\@{{LOAD_SERVERS $servers[0]\n"; # to preselect the same servers as those selected in the parnet window<br /> <br /> print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=SEM_Development_Guide&diff=354 SEM Development Guide 2011-03-28T15:33:24Z

<p>Mike.schofield: </p> <hr /> <div>== Introduction to the SEM Development Guide ==<br /> <br /> Welcome to the Sysgem Enterprise Manager (SEM) Development Guide! <br /> <br /> 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. <br /> <br /> 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:<br /> <br /> * Linux / UNIX ([http://en.wikipedia.org/wiki/Korn_shell Korn Shell])<br /> <br /> * OpenVMS ([http://en.wikipedia.org/wiki/DIGITAL_Command_Language DCL])<br /> <br /> * OS/400 ([http://en.wikipedia.org/wiki/AS/400_Control_Language CL])<br /> <br /> <br /> == Overview of SEM Components ==<br /> <br /> This section 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:<br /> <br /> * SEM Authorization Server<br /> <br /> * SEM Management Console (GUI)<br /> <br /> * SEM Agents<br /> <br /> An overview of the Sysgem Enterprise Manager(SEM) framework is decribed on the [[SEM Overview]] page.<br /> <br /> <br /> == Start the SEM Development Interface ==<br /> <br /> This section describes how to edit either your own private SEM library or a SEM Module library that is available to all users of the SEM system.<br /> <br /> Before you can access the SEM Development Interface the following three conditions need to be satisfied:<br /> <br /> * Your SEM License has to contain the permission to use the Development Interface<br /> <br /> * The SEM 'Master Profile' on your system needs to have the permission set<br /> <br /> * The SEM 'User Profile' allocated to your SEM account needs to have the permission set<br /> <br /> To learn how to set up and start the SEM Development Interface please read the [[Start SEM Development Interface]] page.<br /> <br /> <br /> == Navigate the SEM Development Interface ==<br /> <br /> This section describes the features available to the SEM Developer and how to navigate around a SEM library.<br /> <br /> The first display shown after selecting the "Edit" ( [[File:DevBlueHammer.jpg]] ) option is a list of "Custom Display Windows" that are contained within the library.<br /> <br /> Editing a Custom Display gives the following 'property' pages<br /> <br /> * General Page<br /> <br /> * Startup Page<br /> <br /> * Service Display Page<br /> <br /> * Data Cache Page<br /> <br /> * Columns Page<br /> <br /> * Layouts Page<br /> <br /> * Common Page<br /> <br /> * Menu Page<br /> <br /> * Drag and Drop Page<br /> <br /> * Scripts Page<br /> <br /> To learn how to create or customize Windows and options within a SEM Module using the SEM Development Interface please read the [[Navigate SEM Development Interface]] page.<br /> <br /> <br /> == SEM User Permissions ==<br /> <br /> A user needs an Account in Sysgem Enterprise Manager (SEM) in order to use the product. A SEM user account needs an "Access Control Profile" to control the level of 'SEM Base Privileges', and an Access Control Profile needs "Access Control Token(s)" to control the level of privileges offered by SEM Module(s).<br /> <br /> The following sections describe how SEM Accounts, Profiles and Tokens are set up and how the settings are accessed by scripts:<br /> <br /> * [[SEM User Accounts]] (How to set up a SEM User Account)<br /> <br /> * [[Access Control Profiles]] (Access Control Profiles are allocated to a 'SEM User' to control what 'SEM Base Privileges' are available)<br /> <br /> * [[Access Control Tokens]] (Access Control Tokens are allocated to a 'Profile' to control what 'SEM Module Privileges' are available)<br /> <br /> <br /> == Developer Examples ==<br /> <br /> Below is a list of topics giving tips and programming examples to help the SEM Developer:<br /> <br /> <br /> '''''Defining the Characteristics of an Input Form:'''''<br /> <br /> * [[Field Definitions]]. (How to create and set up the permanent characteristics of fields on a SEM input form using the SEM Development Interface.)<br /> <br /> * [[Change Input Field View]]. (How to dynamically change the view of fields on a SEM input form from the "Fields" script.)<br /> <br /> <br /> '''''Input Variables Preset in Scripts by the SEM Framework:'''''<br /> <br /> * [[Script Input Variables]]. (Script variables preset by the SEM framework before a script is run and then available as input to the script.)<br /> <br /> <br /> '''''Controlling Subsequent Actions After a Script has Run:'''''<br /> <br /> * [[Start-up Initialization]]. (Setting Values in the Start-up window of a SEM Display)<br /> <br /> * [[Suppress Agent Output in Post-process]]. (Normal output from the SEM Agent may be intercepted and modified by Post-processing) <br /> <br /> * [[Dialogue Boxes]]. (Display Information/warning/error messages in a pop-up box.)<br /> <br /> * [[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.)<br /> <br /> * [[AUTO_CLOSE]] command. (Automatically close the input form after a transaction is complete.)<br /> <br /> * [[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.)<br /> <br /> <br /> '''''Passing Data to a Main Target Agent Script'''''<br /> <br /> * [[Main Display Pre-Processing Script Output]] (Passing data to the main target agent script when a SEM display is started)<br /> <br /> * [[ADD_SVR from a menu Pre-Process]] (Passing data to the main target agent script when a SEM Menu Option is run)<br /> <br /> <br /> <br /> '''''Retrieving Data from the Central Options Cache'''''<br /> <br /> * [[Fetch From Options Cache]] (Fetching data from the Authorization Server Options Cache)<br /> <br /> <br /> <br /> '''''Starting a 'Child' Window from a menu option on a 'Parent' Window'''''<br /> <br /> * [[Spawning a Child Window]] (Spawn a child window and pass data for display from the parent)</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Capturing_Log_File_Data_in_SEM&diff=353 Capturing Log File Data in SEM 2011-03-08T22:05:49Z

<p>Mike.schofield: </p> <hr /> <div>'''''Log File Data to Help Diagnose a Problem or Answer a Question in SEM'''''<br /> <br /> <br /> When submitting a customer problem-report or asking a question regarding an incident in SEM it is always helpful for Sysgem to be given details of the event as recorded in the SEM Log File. This page describes where to extract that information. Please send the content of the Log File to Sysgem with any SEM problem report.<br /> <br /> <br /> '''To keep the log file to manageable proportions when submitting a report:'''<br /> <br /> <br /> 1. Log into SEM.<br /> <br /> 2. Open the Log File window by pressing the “Log” icon at the top of the SEM desktop. <br /> <br /> [[File:LogFile1.jpg]]<br /> <br /> 3. Select the Trace Tab and make sure the “Send” and “Recv” buttons are selected (pressed in).<br /> <br /> [[File:LogFile2.jpg]]<br /> <br /> 4. Start the window that has the problem and use it up to the point just BEFORE it fails. Then go back to the Logfile Trace window<br /> <br /> <br /> 5. Remove any data already displayed in the Trace tab window by pressing the “Erase” button next to the “Send” button.<br /> <br /> <br /> 6. Resume the action on the problem window until the error occurs.<br /> <br /> <br /> 7. Expand the Log Data<br /> <br /> [[File:LogFile3.jpg]]<br /> <br /> 8. Finally, “Export” the content of the log window as a text file and send the text file to support@sysgem.com together with a description of the problem. When exporting the file please use the “Text Document” and “Single-column, no border” format as shown in the two highlighted fields below:<br /> <br /> [[File:LogFile4.jpg]]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Main_Page&diff=352 Main Page 2011-03-08T17:52:42Z

<p>Mike.schofield: </p> <hr /> <div>== Welcome to the Sysgem Support Wiki ==<br /> <br /> <br /> This wiki is intended to contain useful information for those involved in supporting, developing or customising Sysgem products. <br /> <br /> It is currently in a draft state; for real support issues we recommend that you contact us using our normal support channels:<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Customer Support]<br /> * [http://www.sysgem.com/company.php#contactus Contact Sysgem]<br /> <br /> The content on this wiki is visible to everyone, to provide maximum benefit to our customers and colleagues. <br /> <br /> However, to add or edit content, a user account is required; if you wish to contribute any information, please contact Sysgem.<br /> <br /> <br /> <br /> == '''Contents''' ==<br /> <br /> <br /> '''Distributors:'''<br /> <br /> * [[Become a SEM Distributor]] contains useful information for potential distributors and resellers of Sysgem products<br /> <br /> '''Development:'''<br /> <br /> * [[SEM Development Guide]] contains example code for developers working within the SEM environment<br /> <br /> '''Support:'''<br /> <br /> * [[Capturing Log File Data in SEM]] for proving diagnostic information to Sysgem when a problem or question arises<br /> <br /> * [[PwdReset Product Support]] for support issues relating to Sysgem Self Service Password Reset<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Support] for general support issues*, please read [[Capturing Log File Data in SEM]] first<br /> <br /> * [http://www.sysgem.com/support/faq.php FAQs] for frequently asked questions*<br /> <br /> * [http://www.sysgem.com/support/casestudies.php Case Studies] for case studies*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMQuickStartGuide.pdf Quick Start] for the SEM Quick Start Guide*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMWhitePaperRev2.pdf SEM White Paper] for the Sysgem Enterprise Manager White Paper*<br /> <br /> '''Announcements:'''<br /> <br /> * [[Announcing SEM V3.0]] contains a description of the architecture being developed in the SEM v3.0 release.<br /> <br /> <br /> Note: *** Items marked with * indicate that they are links to objects on the Sysgem web site - not (yet) wiki pages.<br /> <br /> <br /> <br /> ----<br /> <br /> <br /> '''Help in using this wiki'''<br /> <br /> Consult the [http://meta.wikimedia.org/wiki/Help:Contents Wiki User's Guide] for information on using the wiki software.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Capturing_Log_File_Data_in_SEM&diff=351 Capturing Log File Data in SEM 2011-03-08T16:37:50Z

<p>Mike.schofield: </p> <hr /> <div>'''''Log File Data to Help Diagnose a Problem or Answer a Question in SEM'''''<br /> <br /> <br /> When submitting a customer problem-report or asking a question regarding an incident in SEM it is always helpful for Sysgem to be given details of the event as recorded in the SEM Log File. This page describes where to extract that information. Please send the content of the Log File to Sysgem with any SEM problem report.<br /> <br /> <br /> '''To keep the log file to manageable proportions when submitting a report:'''<br /> <br /> <br /> 1. Log into SEM.<br /> <br /> [[File:LogFile1.jpg]]<br /> <br /> 2. Open the Log File window by pressing the “Log” icon at the top of the SEM desktop. <br /> <br /> [[File:LogFile2.jpg]]<br /> <br /> 3. Select the Trace Tab and make sure the “Send” and “Recv” buttons are selected (pressed in).<br /> <br /> <br /> 4. Start the window that has the problem and use it up to the point just BEFORE it fails. Then go back to the Logfile Trace window<br /> <br /> <br /> 5. Remove any data already displayed in the Trace tab window by pressing the “Erase” button next to the “Send” button.<br /> <br /> <br /> 6. Resume the action on the problem window until the error occurs.<br /> <br /> <br /> 7. Expand the Log Data<br /> <br /> [[File:LogFile3.jpg]]<br /> <br /> 8. Finally, “Export” the content of the log window as a text file and send the text file to support@sysgem.com together with a description of the problem. When exporting the file please use the “Text Document” and “Single-column, no border” format as shown in the two highlighted fields below:<br /> <br /> [[File:LogFile4.jpg]]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Capturing_Log_File_Data_in_SEM&diff=350 Capturing Log File Data in SEM 2011-03-08T16:36:39Z

<p>Mike.schofield: </p> <hr /> <div>'''''Log File Data to Help Diagnose a Problem or Answer a Question in SEM'''''<br /> <br /> <br /> When submitting a customer problem-report or asking a question regarding an incident in SEM it is always helpful for Sysgem to be given details of the event as recorded in the SEM Log File. This page describes where to extract that information. Please send the content of the Log File with any SEM problem report to Sysgem.<br /> <br /> <br /> '''To keep the log file to manageable proportions when submitting a report:'''<br /> <br /> <br /> 1. Log into SEM.<br /> <br /> [[File:LogFile1.jpg]]<br /> <br /> 2. Open the Log File window by pressing the “Log” icon at the top of the SEM desktop. <br /> <br /> [[File:LogFile2.jpg]]<br /> <br /> 3. Select the Trace Tab and make sure the “Send” and “Recv” buttons are selected (pressed in).<br /> <br /> <br /> 4. Start the window that has the problem and use it up to the point just BEFORE it fails. Then go back to the Logfile Trace window<br /> <br /> <br /> 5. Remove any data already displayed in the Trace tab window by pressing the “Erase” button next to the “Send” button.<br /> <br /> <br /> 6. Resume the action on the problem window until the error occurs.<br /> <br /> <br /> 7. Expand the Log Data<br /> <br /> [[File:LogFile3.jpg]]<br /> <br /> 8. Finally, “Export” the content of the log window as a text file and send the text file to support@sysgem.com together with a description of the problem. When exporting the file please use the “Text Document” and “Single-column, no border” format as shown in the two highlighted fields below:<br /> <br /> [[File:LogFile4.jpg]]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Capturing_Log_File_Data_in_SEM&diff=349 Capturing Log File Data in SEM 2011-03-08T16:35:32Z

<p>Mike.schofield: </p> <hr /> <div>'''''Log File Data to Help Diagnose a Problem or Answer a Question in SEM'''''<br /> <br /> <br /> When submitting a customer problem-report or asking a question regarding an incident in SEM it is always helpful for Sysgem to be given details of the event as recorded in the SEM Log File. This page describes where to extract that information. Please send the content of the Log File with any SEM problem report submitted to Sysgem.<br /> <br /> <br /> '''To keep the log file to manageable proportions when submitting a report:'''<br /> <br /> <br /> 1. Log into SEM.<br /> <br /> [[File:LogFile1.jpg]]<br /> <br /> 2. Open the Log File window by pressing the “Log” icon at the top of the SEM desktop. <br /> <br /> [[File:LogFile2.jpg]]<br /> <br /> 3. Select the Trace Tab and make sure the “Send” and “Recv” buttons are selected (pressed in).<br /> <br /> <br /> 4. Start the window that has the problem and use it up to the point just BEFORE it fails. Then go back to the Logfile Trace window<br /> <br /> <br /> 5. Remove any data already displayed in the Trace tab window by pressing the “Erase” button next to the “Send” button.<br /> <br /> <br /> 6. Resume the action on the problem window until the error occurs.<br /> <br /> <br /> 7. Expand the Log Data<br /> <br /> [[File:LogFile3.jpg]]<br /> <br /> 8. Finally, “Export” the content of the log window as a text file and send the text file to support@sysgem.com together with a description of the problem. When exporting the file please use the “Text Document” and “Single-column, no border” format as shown in the two highlighted fields below:<br /> <br /> [[File:LogFile4.jpg]]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Main_Page&diff=348 Main Page 2011-03-08T16:33:09Z

<p>Mike.schofield: </p> <hr /> <div>== Welcome to the Sysgem Support Wiki ==<br /> <br /> <br /> This wiki is intended to contain useful information for those involved in supporting, developing or customising Sysgem products. <br /> <br /> It is currently in a draft state; for real support issues we recommend that you contact us using our normal support channels:<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Customer Support]<br /> * [http://www.sysgem.com/company.php#contactus Contact Sysgem]<br /> <br /> The content on this wiki is visible to everyone, to provide maximum benefit to our customers and colleagues. <br /> <br /> However, to add or edit content, a user account is required; if you wish to contribute any information, please contact Sysgem.<br /> <br /> <br /> <br /> == '''Contents''' ==<br /> <br /> <br /> '''Distributors:'''<br /> <br /> * [[Become a SEM Distributor]] contains useful information for potential distributors and resellers of Sysgem products<br /> <br /> '''Development:'''<br /> <br /> * [[SEM Development Guide]] contains example code for developers working within the SEM environment<br /> <br /> '''Support:'''<br /> <br /> * [[Capturing Log File Data in SEM]] for proving diagnostic information to Sysgem when an problem or question arises<br /> <br /> * [[PwdReset Product Support]] for support issues relating to Sysgem Self Service Password Reset<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Support] for general support issues*, please read [[Capturing Log File Data in SEM]] first<br /> <br /> * [http://www.sysgem.com/support/faq.php FAQs] for frequently asked questions*<br /> <br /> * [http://www.sysgem.com/support/casestudies.php Case Studies] for case studies*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMQuickStartGuide.pdf Quick Start] for the SEM Quick Start Guide*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMWhitePaperRev2.pdf SEM White Paper] for the Sysgem Enterprise Manager White Paper*<br /> <br /> '''Announcements:'''<br /> <br /> * [[Announcing SEM V3.0]] contains a description of the architecture being developed in the SEM v3.0 release.<br /> <br /> <br /> Note: *** Items marked with * indicate that they are links to objects on the Sysgem web site - not (yet) wiki pages.<br /> <br /> <br /> <br /> ----<br /> <br /> <br /> '''Help in using this wiki'''<br /> <br /> Consult the [http://meta.wikimedia.org/wiki/Help:Contents Wiki User's Guide] for information on using the wiki software.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Main_Page&diff=347 Main Page 2011-03-08T16:31:57Z

<p>Mike.schofield: </p> <hr /> <div>== Welcome to the Sysgem Support Wiki ==<br /> <br /> <br /> This wiki is intended to contain useful information for those involved in supporting, developing or customising Sysgem products. <br /> <br /> It is currently in a draft state; for real support issues we recommend that you contact us using our normal support channels:<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Customer Support]<br /> * [http://www.sysgem.com/company.php#contactus Contact Sysgem]<br /> <br /> The content on this wiki is visible to everyone, to provide maximum benefit to our customers and colleagues. <br /> <br /> However, to add or edit content, a user account is required; if you wish to contribute any information, please contact Sysgem.<br /> <br /> <br /> <br /> == '''Contents''' ==<br /> <br /> <br /> '''Distributors:'''<br /> <br /> * [[Become a SEM Distributor]] contains useful information for potential distributors and resellers of Sysgem products<br /> <br /> '''Development:'''<br /> <br /> * [[SEM Development Guide]] contains example code for developers working within the SEM environment<br /> <br /> '''Support:'''<br /> <br /> * [[Capturing Log File Data in SEM]] for proving diagnostic information to Sysgem when an problem or question arises<br /> <br /> * [[PwdReset Product Support]] for support issues relating to Sysgem Self Service Password Reset<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Support] for general support issues, please read [[Capturing Log File Data in SEM]] first*<br /> <br /> * [http://www.sysgem.com/support/faq.php FAQs] for frequently asked questions*<br /> <br /> * [http://www.sysgem.com/support/casestudies.php Case Studies] for case studies*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMQuickStartGuide.pdf Quick Start] for the SEM Quick Start Guide*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMWhitePaperRev2.pdf SEM White Paper] for the Sysgem Enterprise Manager White Paper*<br /> <br /> '''Announcements:'''<br /> <br /> * [[Announcing SEM V3.0]] contains a description of the architecture being developed in the SEM v3.0 release.<br /> <br /> <br /> Note: *** Items marked with * indicate that they are links to objects on the Sysgem web site - not (yet) wiki pages.<br /> <br /> <br /> <br /> ----<br /> <br /> <br /> '''Help in using this wiki'''<br /> <br /> Consult the [http://meta.wikimedia.org/wiki/Help:Contents Wiki User's Guide] for information on using the wiki software.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Capturing_Log_File_Data_in_SEM&diff=346 Capturing Log File Data in SEM 2011-03-08T16:15:10Z

<p>Mike.schofield: </p> <hr /> <div>'''''Log File Data to Help Diagnose a Problem or Answer a Question in SEM'''''<br /> <br /> <br /> When making a customer report for a problem or asking a question regarding an incident in SEM it is always helpful for Sysgem to be given details of the event as recorded in the SEM Log File. This page describes where to extract that information. Please send the content of the Log File with any SEM problem report submitted to Sysgem.<br /> <br /> <br /> '''To keep the log file to manageable proportions when submitting a report:'''<br /> <br /> <br /> 1. Log into SEM.<br /> <br /> [[File:LogFile1.jpg]]<br /> <br /> 2. Open the Log File window by pressing the “Log” icon at the top of the SEM desktop. <br /> <br /> [[File:LogFile2.jpg]]<br /> <br /> 3. Select the Trace Tab and make sure the “Send” and “Recv” buttons are selected (pressed in).<br /> <br /> <br /> 4. Start the window that has the problem and use it up to the point just BEFORE it fails. Then go back to the Logfile Trace window<br /> <br /> <br /> 5. Remove any data already displayed in the Trace tab window by pressing the “Erase” button next to the “Send” button.<br /> <br /> <br /> 6. Resume the action on the problem window until the error occurs.<br /> <br /> <br /> 7. Expand the Log Data<br /> <br /> [[File:LogFile3.jpg]]<br /> <br /> 8. Finally, “Export” the content of the log window as a text file and send the text file to support@sysgem.com together with a description of the problem. When exporting the file please use the “Text Document” and “Single-column, no border” format as shown in the two highlighted fields below:<br /> <br /> [[File:LogFile4.jpg]]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Capturing_Log_File_Data_in_SEM&diff=345 Capturing Log File Data in SEM 2011-03-08T16:11:34Z

<p>Mike.schofield: Created page with "'''''Log File Data to Help Diagnose a Problem or Answer a Question in SEM''''' When making a customer report for a problem or asking a question regarding an incident in SEM it ..."</p> <hr /> <div>'''''Log File Data to Help Diagnose a Problem or Answer a Question in SEM'''''<br /> <br /> <br /> When making a customer report for a problem or asking a question regarding an incident in SEM it is always helpful for Sysgem to be given details of the event as recorded in the SEM Log File. This page describes where to extract that information. Please send the content of the Log File with any SEM problem report submitted to Sysgem.<br /> <br /> <br /> '''To keep the log file to manageable proportions when submitting a report:'''<br /> <br /> <br /> 1. Log into SEM.<br /> <br /> [[File:LogFile1.jpg]]<br /> <br /> <br /> 2. Open the Log File window by pressing the “Log” icon at the top of the SEM desktop. <br /> <br /> [[File:LogFile2.jpg]]<br /> <br /> 3. Select the Trace Tab and make sure the “Send” and “Recv” buttons are selected (pressed in).<br /> <br /> <br /> 4. Start the window that has the problem and use it up to the point just BEFORE it fails. Then go back to the Logfile Trace window<br /> <br /> <br /> 5. Remove any data already displayed in the Trace tab window by pressing the “Erase” button next to the “Send” button.<br /> <br /> 6. Resume the action on the problem window until the error occurs.<br /> <br /> <br /> 7. Expand the Log Data<br /> <br /> [[File:LogFile3.jpg]]<br /> <br /> 6. Finally, “Export” the content of the log window as a text file and send the text file to support@sysgem.com together with a description of the problem. When exporting the file please use the “Text Document” and “Single-column, no border” format as shown in the two highlighted fields below:<br /> <br /> <br /> [[File:LogFile4.jpg]]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=File:LogFile1.jpg&diff=344 File:LogFile1.jpg 2011-03-08T16:09:27Z

<p>Mike.schofield: </p> <hr /> <div></div>

Mike.schofield https://wiki.sysgem.com/index.php?title=File:LogFile4.jpg&diff=343 File:LogFile4.jpg 2011-03-08T16:02:35Z

<p>Mike.schofield: </p> <hr /> <div></div>

Mike.schofield https://wiki.sysgem.com/index.php?title=File:LogFile3.jpg&diff=342 File:LogFile3.jpg 2011-03-08T16:02:12Z

<p>Mike.schofield: </p> <hr /> <div></div>

Mike.schofield https://wiki.sysgem.com/index.php?title=File:LogFile2.jpg&diff=341 File:LogFile2.jpg 2011-03-08T16:01:47Z

<p>Mike.schofield: </p> <hr /> <div></div>

Mike.schofield https://wiki.sysgem.com/index.php?title=File:LoFile1.jpg&diff=340 File:LoFile1.jpg 2011-03-08T16:01:29Z

<p>Mike.schofield: </p> <hr /> <div></div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Main_Page&diff=339 Main Page 2011-03-08T15:37:18Z

<p>Mike.schofield: </p> <hr /> <div>== Welcome to the Sysgem Support Wiki ==<br /> <br /> <br /> This wiki is intended to contain useful information for those involved in supporting, developing or customising Sysgem products. <br /> <br /> It is currently in a draft state; for real support issues we recommend that you contact us using our normal support channels:<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Customer Support]<br /> * [http://www.sysgem.com/company.php#contactus Contact Sysgem]<br /> <br /> The content on this wiki is visible to everyone, to provide maximum benefit to our customers and colleagues. <br /> <br /> However, to add or edit content, a user account is required; if you wish to contribute any information, please contact Sysgem.<br /> <br /> <br /> <br /> == '''Contents''' ==<br /> <br /> <br /> '''Distributors:'''<br /> <br /> * [[Become a SEM Distributor]] contains useful information for potential distributors and resellers of Sysgem products<br /> <br /> '''Development:'''<br /> <br /> * [[SEM Development Guide]] contains example code for developers working within the SEM environment<br /> <br /> '''Support:'''<br /> <br /> * [[Capturing Log File Data in SEM]] for proving diagnostic information to Sysgem when an problem or question arises<br /> <br /> * [[PwdReset Product Support]] for support issues relating to Sysgem Self Service Password Reset<br /> <br /> * [http://www.sysgem.com/support.php Sysgem Support] for general support issues*<br /> <br /> * [http://www.sysgem.com/support/faq.php FAQs] for frequently asked questions*<br /> <br /> * [http://www.sysgem.com/support/casestudies.php Case Studies] for case studies*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMQuickStartGuide.pdf Quick Start] for the SEM Quick Start Guide*<br /> <br /> * [http://www.sysgem.com/uploaded_files/productguides/SEMWhitePaperRev2.pdf SEM White Paper] for the Sysgem Enterprise Manager White Paper*<br /> <br /> '''Announcements:'''<br /> <br /> * [[Announcing SEM V3.0]] contains a description of the architecture being developed in the SEM v3.0 release.<br /> <br /> <br /> Note: *** Items marked with * indicate that they are links to objects on the Sysgem web site that have not yet been implemented using wiki.<br /> <br /> <br /> <br /> ----<br /> <br /> <br /> '''Help in using this wiki'''<br /> <br /> Consult the [http://meta.wikimedia.org/wiki/Help:Contents Wiki User's Guide] for information on using the wiki software.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Web_Server_Component&diff=338 Web Server Component 2011-03-02T13:55:10Z

<p>Mike.schofield: </p> <hr /> <div>'''''Issues relating to the installation of the web component of Sysgem Self-Service Password Reset''''' <br /> <br /> Microsoft Internet Information Services (IIS) needs to be installed and running in order for the web service component of ''Sysgem Self-Service Password Reset'' to install correctly.<br /> <br /> <br /> <br /> '''Is Microsoft Internet Information Services Installed?'''<br /> <br /> One of the simplest and surest ways to determine whether IIS is installed is to check the registry entry for: <br /> <br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp <br /> <br /> If it exists then it is installed, if it does not exists, then IIS is not installed.<br /> <br /> If IIS is not installed, then install it by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Add/Remove Programs<br /> <br /> 3) Open Add/Remove Windows Components<br /> <br /> 2) Place a tick in the check box for 'Internet Information Services (IIS)' leaving all the default installation settings intact.<br /> <br /> <br /> '''Is Microsoft Internet Information Services Running?'''<br /> <br /> Check to see if IIS is running by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Administrative Tools<br /> <br /> 3) Open Computer Management<br /> <br /> 4) Open Services and Applications (expand the tree)<br /> <br /> 5) Open Internet Information Services (expand the tree)<br /> <br /> 6) Open the 'Web Sites' folder <br /> <br /> 7) Check if "Default Web Site" is running. If not, then start it.<br /> <br /> <br /> '''Is Microsoft Internet Information Services configured correctly?'''<br /> <br /> Ensure that the administrative routines needed by the Sysgem Self-Service Password Reset installer are enabled.<br /> <br /> Check [[IIS Configuration]] to ensure that the IIS administrative routines are enabled.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=IIS_Configuration&diff=337 IIS Configuration 2011-03-02T13:22:10Z

<p>Mike.schofield: </p> <hr /> <div>'''''A description of the Microsoft Internet Information Services configuration needed for the installation of Sysgem Self-Service Password Reset'''''<br /> <br /> <br /> <br /> '''IIS Admin Routines'''<br /> <br /> Recent versions of Microsoft Internet Information Services (IIS) do not, by default, expose the administrative routines that the Sysgem Self-Service Password Reset installer uses to configure the Web Site.<br /> <br /> The IIS administrative routines need to be enabled before launching the Sysgem installation.<br /> <br /> Enable the routines by using the Windows 'Add Features' option (in the Control Panel or the Server Manager). They are listed as 'IIS 6 Management Tools' with several suboptions including 'Metabase Compatibility'. Once these are installed the setup routine of the Sysgem Self-Service Password Reset installer should be able to create the web pages.<br /> <br /> <br /> '''Permissions on Files and the Account Used for Annoymous Access'''<br /> <br /> There are two files to which the Self Service Password reset setup program adds permissions:<br /> <br /> <br /> * C:\Program Files\Sysgem AG\Password Reset\Web\license.txt<br /> * C:\Program Files\Sysgem AG\Password Reset\Database\SEMPwdResetSvr.txt<br /> <br /> <br /> (* Where C:\Program Files\Sysgem AG\Password Reset can vary based on 64/32-bit and international versions of Windows, or a custom directory can be specified during installation.)<br /> <br /> The IUSR account needs write access to these files. Without that permission, the license will not be created correctly and an error message will be displayed.<br /> <br /> Check the account that is used for Annonymous Access by using the IIS Management Tool (from the Control Panel, Administrator Tools)<br /> <br /> 1) Drill down to the PwdReset directory (typically SERVERNAME -> Sites-> Default Web Site -> pwdreset)<br /> <br /> 2) Open the Authentication category (or "Directory Security" on the pwdreset Property Page)<br /> <br /> 3) Right-click Anonymous Authentication and select Edit<br /> <br /> 4) The resulting dialog box should indicate the user account that's being used to write to Password Reset's license and Q&A list.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=IIS_Configuration&diff=336 IIS Configuration 2011-03-01T15:34:28Z

<p>Mike.schofield: </p> <hr /> <div>'''''A description of the Microsoft Internet Information Services configuration needed for the installation of Sysgem Self-Service Password Reset'''''<br /> <br /> <br /> <br /> Recent versions of Microsoft Internet Information Services (IIS) do not, by default, expose the administrative routines that the Sysgem Self-Service Password Reset installer uses to configure the Web Site.<br /> <br /> The IIS administrative routines need to be enabled before launching the Sysgem installation.<br /> <br /> Enable the routines by using the Windows 'Add Features' option (in the Control Panel or the Server Manager). They are listed as 'IIS 6 Management Tools' with several suboptions including 'Metabase Compatibility'. Once these are installed the setup routine of the Sysgem Self-Service Password Reset installer should be able to create the web pages.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Installation_Password&diff=335 Installation Password 2011-03-01T15:31:42Z

<p>Mike.schofield: </p> <hr /> <div>'''For the Installation Password to the latest '' 'Sysgem Self-Service Password Reset' '' kit, please contact Sysgem Support using the following link:'''<br /> <br /> <br /> [http://www.sysgem.com/form.php?view=form_support mailto: Sysgem]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Installation_Password&diff=334 Installation Password 2011-03-01T15:31:07Z

<p>Mike.schofield: </p> <hr /> <div>'''For the Installation Password to the latest '' 'Sysgem Self-Service Password Reset' '' kit, please contact Sysgem Support on:'''<br /> <br /> <br /> [http://www.sysgem.com/form.php?view=form_support mailto: Sysgem]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Installation_Password&diff=333 Installation Password 2011-03-01T15:29:26Z

<p>Mike.schofield: </p> <hr /> <div>'''For the Installation Password to the latest ''Sysgem Self-Service Password Reset'' kit, please contact:'''<br /> <br /> <br /> [http://www.sysgem.com/form.php?view=form_support mailto: Sysgem]</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=PwdReset_Product_Support&diff=332 PwdReset Product Support 2011-03-01T15:28:55Z

<p>Mike.schofield: </p> <hr /> <div>'''''Support Issues Relating to Sysgem Self-Service Password Reset'''''<br /> <br /> <br /> Sysgem Self-Service Password Reset allows users to reset forgotten passwords after correctly replying to memorable questions with answers that they, themselves, have previously defined. This solution is for installation on Microsoft Windows running on workstations, servers and Active Directory domains. For a full description of Sysgem Self-Service Password Reset see: [http://www.sysgem.com/products/sspwdreset.php?view=sspwdreset_tabdefault Self-Service Password Reset].<br /> <br /> <br /> '''Installation Questions:'''<br /> <br /> * [[Installation Password]] - Please Contact Sysgem for the Installation Password for Sysgem Self-Service Password Reset<br /> <br /> * [[Supported Windows Versions]] - A list of MS Windows versions supported by Sysgem Self-Service Password Reset<br /> <br /> * [[Web Server Component]] - Issues relating to the installation of the web component of Sysgem Self-Service Password Reset<br /> <br /> * [[IIS Configuration]] - A description of the Microsoft ''Internet Information Services'' configuration needed for the installation of Sysgem Self-Service Password Reset</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Web_Server_Component&diff=331 Web Server Component 2011-03-01T15:27:51Z

<p>Mike.schofield: </p> <hr /> <div>'''''Issues relating to the installation of the web component of Sysgem Self-Service Password Reset''''' <br /> <br /> Microsoft Internet Information Services (IIS) needs to be installed and running in order for the web service component of ''Sysgem Self-Service Password Reset'' to install correctly.<br /> <br /> <br /> <br /> '''Is Microsoft Internet Information Services Installed?'''<br /> <br /> One of the simplest and surest ways to determine whether IIS is installed is to check the registry entry for: <br /> <br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp <br /> <br /> If it exists then it is installed, if it not exists, then IIS is not installed.<br /> <br /> If IIS is not installed, then install it by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Add/Remove Programs<br /> <br /> 3) Open Add/Remove Windows Components<br /> <br /> 2) Place a tick in the check box for 'Internet Information Services (IIS)' leaving all the default installation settings intact.<br /> <br /> <br /> '''Is Microsoft Internet Information Services Running?'''<br /> <br /> Check to see if IIS is running by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Administrative Tools<br /> <br /> 3) Open Computer Management<br /> <br /> 4) Open Services and Applications (expand the tree)<br /> <br /> 5) Open Internet Information Services (expand the tree)<br /> <br /> 6) Open the 'Web Sites' folder <br /> <br /> 7) Check if "Default Web Site" is running. If not, then start it.<br /> <br /> <br /> '''Is Microsoft Internet Information Services configured correctly?'''<br /> <br /> Ensure that the administrative routines needed by the Sysgem Self-Service Password Reset installer are enabled.<br /> <br /> Check [[IIS Configuration]] to ensure that the IIS administrative routines are enabled.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=IIS_Configuration&diff=330 IIS Configuration 2011-03-01T15:23:26Z

<p>Mike.schofield: Created page with "'''''A description of the Microsoft Internet Information Services configuration needed for the installation of Sysgem Self-Service Password Reset''''' Recent versions of Micro..."</p> <hr /> <div>'''''A description of the Microsoft Internet Information Services configuration needed for the installation of Sysgem Self-Service Password Reset'''''<br /> <br /> <br /> <br /> Recent versions of Microsoft Internet Information Services (IIS) do not, by default, expose the administrative routines that the Sysgem Self-Service Password Reset installer uses to configure the Web Site.<br /> <br /> They IIS administrative routines need to be enabled before launching the Sysgem installation.<br /> <br /> Enable the routines by using the Windows 'Add Features' option (in the Control Panel or the Server Manager). They are listed as 'IIS 6 Management Tools' with several suboptions including 'Metabase Compatibility'. Once these are installed the setup routine of the Sysgem Self-Service Password Reset installer should be able to create the web pages.</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Web_Server_Component&diff=329 Web Server Component 2011-03-01T15:11:38Z

<p>Mike.schofield: </p> <hr /> <div>'''''Issues relating to the installation of the web component of Sysgem Self-Service Password Reset''''' <br /> <br /> Microsoft Internet Information Services (IIS) needs to be installed and running in order for the web service component of ''Sysgem Self-Service Password Reset'' to install correctly.<br /> <br /> <br /> <br /> '''Is Microsoft Internet Information Services Installed?'''<br /> <br /> One of the simplest and surest ways to determine whether IIS is installed is to check the registry entry for: <br /> <br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp <br /> <br /> If it exists then it is installed, if it not exists, then IIS is not installed.<br /> <br /> If IIS is not installed, then install it by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Add/Remove Programs<br /> <br /> 3) Open Add/Remove Windows Components<br /> <br /> 2) Place a tick in the check box for 'Internet Information Services (IIS)' leaving all the default installation settings intact.<br /> <br /> <br /> '''Is Microsoft Internet Information Services Running?'''<br /> <br /> Check to see if IIS is running by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Administrative Tools<br /> <br /> 3) Open Computer Management<br /> <br /> 4) Open Services and Applications (expand the tree)<br /> <br /> 5) Open Internet Information Services (expand the tree)<br /> <br /> 6) Open the 'Web Sites' folder <br /> <br /> 7) Check if "Default Web Site" is running. If not, then start it.<br /> <br /> <br /> '''Is Microsoft Internet Information Services configured correctly?'''</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Web_Server_Component&diff=328 Web Server Component 2011-03-01T15:10:00Z

<p>Mike.schofield: Created page with "'''''Issues relating to the installation of the web component of Sysgem Self-Service Password Reset''''' Microsoft Internet Information Services (IIS) needs to be installed and..."</p> <hr /> <div>'''''Issues relating to the installation of the web component of Sysgem Self-Service Password Reset''''' <br /> <br /> Microsoft Internet Information Services (IIS) needs to be installed and running in order for the web service component of Sysgem Self-Service Password Reset to install correctly.<br /> <br /> <br /> <br /> '''Is Microsoft Internet Information Services Installed?'''<br /> <br /> One of the simplest and surest ways to determine whether IIS is installed is to check the registry entry for: <br /> <br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp <br /> <br /> If it exists then it is installed, if it not exists, then IIS is not installed.<br /> <br /> If IIS is not installed, then install it by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Add/Remove Programs<br /> <br /> 3) Open Add/Remove Windows Components<br /> <br /> 2) Place a tick in the check box for 'Internet Information Services (IIS)' leaving all the default installation settings intact.<br /> <br /> <br /> '''Is Microsoft Internet Information Services Running?'''<br /> <br /> Check to see if IIS is running by:<br /> <br /> 1) Go to the Control Panel<br /> <br /> 2) Open Administrative Tools<br /> <br /> 3) Open Computer Management<br /> <br /> 4) Open Services and Applications (expand the tree)<br /> <br /> 5) Open Internet Information Services (expand the tree)<br /> <br /> 6) Open the 'Web Sites' folder <br /> <br /> 7) Check if "Default Web Site" is running. If not, then start it.<br /> <br /> <br /> '''Is Microsoft Internet Information Services configured correctly?'''</div>

Mike.schofield https://wiki.sysgem.com/index.php?title=Supported_Windows_Versions&diff=327 Supported Windows Versions 2011-03-01T13:01:13Z

<p>Mike.schofield: </p> <hr /> <div>'''''MS Windows versions supported by Sysgem Self-Service Password Reset'''''<br /> <br /> * Windows 2000<br /> <br /> * Windows 2000 Advanced Server<br /> <br /> * Windows XP<br /> <br /> * Windows Server 2003<br /> <br /> * Windows XP Professional x64 Edition (use the 64 bit version of the kit for '''"Password Reset and Password Policy Enforcer - Windows x64"''' from: [http://www.sysgem.com/downloads.php Sysgem Downloads])<br /> <br /> * Windows Vista<br /> <br /> * Windows Server 2008<br /> <br /> * Windows 7<br /> <br /> * Windows Server 2008 R2</div>

Mike.schofield