(I) Windows - Revision history

Mike.schofield at 09:51, 24 February 2011

2011-02-24T09:51:16Z

← Older revision		Revision as of 09:51, 24 February 2011
Line 1:		Line 1:
	'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.		'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.

	~~== Menu Initialize (I) Windows Script ==~~		----

	''Variables set by the SEM framework:''		''Variables set by the SEM framework:''


			'''Menu Initialize (I) Windows Script'''

	The Perl script: ''Menu Initialize "(I) Windows script"'' runs on the target (Windows) system after a menu option has been selected and BEFORE the display of the input form.		The Perl script: ''Menu Initialize "(I) Windows script"'' runs on the target (Windows) system after a menu option has been selected and BEFORE the display of the input form.

Mike.schofield at 12:47, 18 February 2011

2011-02-18T12:47:02Z

← Older revision		Revision as of 12:47, 18 February 2011
Line 22:		Line 22:
	my $USER_SYSGEM_USERNAME "SYSGEM username"		my $USER_SYSGEM_USERNAME "SYSGEM username"
	my $USER_DISPLAY_VERBOSE "Verbose display option (either 0 or 1)"		my $USER_DISPLAY_VERBOSE "Verbose display option (either 0 or 1)"
	my $CLIENT_BUILD "SEM Client Build (e.g. ~~14178392~~.~~14178388~~ 4459)"		my $CLIENT_BUILD "SEM Client Build (e.g. 2.3 4459)"

Mike.schofield at 10:50, 4 February 2011

2011-02-04T10:50:18Z

← Older revision		Revision as of 10:50, 4 February 2011
Line 1:		Line 1:
	'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.		'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.

	== (I) Windows Script ==		== Menu Initialize (I) Windows Script ==

	''Variables set by the SEM framework:''		''Variables set by the SEM framework:''

	The Perl script: ''"(I) Windows script"'' runs on the target (Windows) system after a menu option has been selected and BEFORE the display of the input form.		The Perl script: ''Menu Initialize "(I) Windows script"'' runs on the target (Windows) system after a menu option has been selected and BEFORE the display of the input form.

	The main purpose of the script is, for example, if this menu option is a user account management option to 'edit' a Windows user account, then this script will run on the target Windows server to extract the latest set of fields from the selected account so that those fields may be displayed in a 'modify' input form and displayed to the user.		The main purpose of the script is, for example, if this menu option is a user account management option to 'edit' a Windows user account, then this script will run on the target Windows server to extract the latest set of fields from the selected account so that those fields may be displayed in a 'modify' input form and displayed to the user.

Mike.schofield at 11:01, 1 February 2011

2011-02-01T11:01:26Z

← Older revision		Revision as of 11:01, 1 February 2011
Line 11:		Line 11:

	'''''Variables:'''''		'''''Variables:'''''

			The details of the variables stored automatically by the SEM framework at the start of script are shown below.

	* Details of the Current SEM User:		* Details of the Current SEM User:

Mike.schofield at 10:47, 1 February 2011

2011-02-01T10:47:35Z

← Older revision		Revision as of 10:47, 1 February 2011
Line 11:		Line 11:

	'''''Variables:'''''		'''''Variables:'''''


	* Details of the Current SEM User:		* Details of the Current SEM User:

Mike.schofield: Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. == (I) Windows Script == ''Variables set by the SEM framework:'' The Perl script: ''"(I) ..."

2011-02-01T10:33:19Z

Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. == (I) Windows Script == ''Variables set by the SEM framework:'' The Perl script: ''"(I) ..."

New page

'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.

== (I) Windows Script ==

''Variables set by the SEM framework:''

The Perl script: ''"(I) Windows script"'' runs on the target (Windows) system after a menu option has been selected and BEFORE the display of the input form.

The main purpose of the script is, for example, if this menu option is a user account management option to 'edit' a Windows user account, then this script will run on the target Windows server to extract the latest set of fields from the selected account so that those fields may be displayed in a 'modify' input form and displayed to the user.

'''''Variables:'''''

* Details of the Current SEM User:

Details of the SEM user that has invoked the menu option are stored in the following Perl variables:

my $USER_NT_USERNAME "Windows NT username"
my $USER_NT_COMPUTER "Windows NT computer name"
my $USER_SYSGEM_USERNAME "SYSGEM username"
my $USER_DISPLAY_VERBOSE "Verbose display option (either 0 or 1)"
my $CLIENT_BUILD "SEM Client Build (e.g. 14178392.14178388 4459)"

* Details of the Target Server:

Details of the target Windows server are displayed in the following Perl variables:

my $SERVER_DEF_NAME "Agent name - from the Agent Definition"
my $SERVER_DEF_DESC "Agent description - from the Agent Definition"
my $SERVER_DEF_ADDR "Agent address - from the Agent Definition"
my $SERVER_DEF_PORT "Agent port - from the Agent Definition"
my $SERVER_DEF_CNTX "Agent context - from the Agent Definition"

* Details of the Current Display Window:

my $SysgemDisplayName "Custom Display Name (e.g. Enterprise Accounts)"
my $SysgemMenuOption "Menu Option (e.g. &Modify)"

* Startup Fields:

The content of the fields entered in the start-up window as the display window was invoked:

my $STARTUP_XX "Where XX is the two character code used in the startup window"

* Selected Entry:

All fields in the selected entry in the display window are recorded as variables. The two character code that defines the field is appended to the VMS System Logical: "ENTRY_" ... for example:

my $ENTRY_SV - holds the Server (Agent) name of the selected record
my $ENTRY_UN - holds the Username of te selected user account

... to see which field codes are used - see the defintion of the display columns in the "Columns" page of SEM development interface.

* Details of the Authorization Server

my $USE_AUTH_SVR_PROXY "Whether the Authorization Server may be used for DB access (either 0 or 1)"
my $AUTH_SVR_ADDRESS "The address of the Authorization Server as used in the SEM Login window"
my $AUTH_SVR_PORT "The port number of the Authorization Server as used in the SEM Login window"