SEM Overview - Revision history

Mike.schofield at 15:32, 21 January 2011

2011-01-21T15:32:12Z

@@ Line 8: / Line 8: @@
 .	Authorization Server: The SEM Authorization Server is at the centre of the SEM architecture. To use SEM, a user has to start the SEM Management Console on their workstation and log into the SEM Authorization Server using a SEM username and password. Each SEM user account has a profile that defines a set of permissions granted to the user. On successfully logging into SEM the appropriate set of SEM display windows and scripts that the user has permission to use are downloaded from the Authorisation Server into the Management Console, and from there will interact with the user and the agents that the user is permitted to connect to. When SEM scripts are created or modified a single, central, copy is retained at the SEM Authorization Server.
 '''Communications'''
 Communications between the three components use a secure encrypted protocol over TCP/IP in SEM versions prior to v3.0. In version 3.0 onwards, the communications between SEM components use Secure Socket Layer ([http://en.wikipedia.org/wiki/SSL SSL]) protocols.

Mike.schofield at 15:28, 21 January 2011

2011-01-21T15:28:34Z

← Older revision		Revision as of 15:28, 21 January 2011
Line 8:		Line 8:

	3. Authorization Server: The SEM Authorization Server is at the centre of the SEM architecture. To use SEM, a user has to start the SEM Management Console on their workstation and log into the SEM Authorization Server using a SEM username and password. Each SEM user account has a profile that defines a set of permissions granted to the user. On successfully logging into SEM the appropriate set of SEM display windows and scripts that the user has permission to use are downloaded from the Authorisation Server into the Management Console, and from there will interact with the user and the agents that the user is permitted to connect to. When SEM scripts are created or modified a single, central, copy is retained at the SEM Authorization Server.		3. Authorization Server: The SEM Authorization Server is at the centre of the SEM architecture. To use SEM, a user has to start the SEM Management Console on their workstation and log into the SEM Authorization Server using a SEM username and password. Each SEM user account has a profile that defines a set of permissions granted to the user. On successfully logging into SEM the appropriate set of SEM display windows and scripts that the user has permission to use are downloaded from the Authorisation Server into the Management Console, and from there will interact with the user and the agents that the user is permitted to connect to. When SEM scripts are created or modified a single, central, copy is retained at the SEM Authorization Server.

			'''Communications'''

			Communications between the three components use a secure encrypted protocol over TCP/IP in SEM versions prior to v3.0. In version 3.0 onwards, the communications between SEM components use Secure Socket Layer ([http://en.wikipedia.org/wiki/SSL SSL]) protocols.

Mike.schofield at 15:14, 21 January 2011

2011-01-21T15:14:53Z

← Older revision		Revision as of 15:14, 21 January 2011
Line 2:		Line 2:

	[[File:SEMComponents_Medium.jpg]]		[[File:SEMComponents_Medium.jpg]]

	1. Management Console: This is installed on Windows workstations and provides the user interface (GUI) to the SEM user.		1. Management Console: This is installed on Windows workstations and provides the user interface (GUI) to the SEM user.

Mike.schofield at 15:14, 21 January 2011

2011-01-21T15:14:36Z

← Older revision		Revision as of 15:14, 21 January 2011
Line 2:		Line 2:

	[[File:SEMComponents_Medium.jpg]]		[[File:SEMComponents_Medium.jpg]]


	1. Management Console: This is installed on Windows workstations and provides the user interface (GUI) to the SEM user.		1. Management Console: This is installed on Windows workstations and provides the user interface (GUI) to the SEM user.

Mike.schofield at 15:04, 21 January 2011

2011-01-21T15:04:24Z

← Older revision		Revision as of 15:04, 21 January 2011
Line 1:		Line 1:
	There are three basic components installed with Sysgem Enterprise Manager (SEM):		There are three basic components installed with Sysgem Enterprise Manager (SEM):

			[[File:SEMComponents_Medium.jpg]]


	1. Management Console: This is installed on Windows workstations and provides the user interface (GUI) to the SEM user.		1. Management Console: This is installed on Windows workstations and provides the user interface (GUI) to the SEM user.
Line 5:		Line 8:
	2. Agents: SEM agents are installed on the target servers that are to be managed. They run as non-interactive processes on the different platform types, they communicate with the Management Consoles and run scripts on demand, passing results to the Management Console for display to the SEM user.		2. Agents: SEM agents are installed on the target servers that are to be managed. They run as non-interactive processes on the different platform types, they communicate with the Management Consoles and run scripts on demand, passing results to the Management Console for display to the SEM user.

	3. Authorization Server: The SEM Authorization Server is at the centre of the SEM architecture. To use SEM, a user has to start the SEM Management Console on their workstation and log into the SEM Authorization Server using a SEM username and password. Each SEM user account has a profile that defines a set of permissions granted to the user. On successfully logging into SEM the appropriate set of SEM display windows and scripts that the user has permission to use are downloaded from the Authorisation Server into the Management Console, and from there will interact with the user and the agents that the user is permitted to connect to.		3. Authorization Server: The SEM Authorization Server is at the centre of the SEM architecture. To use SEM, a user has to start the SEM Management Console on their workstation and log into the SEM Authorization Server using a SEM username and password. Each SEM user account has a profile that defines a set of permissions granted to the user. On successfully logging into SEM the appropriate set of SEM display windows and scripts that the user has permission to use are downloaded from the Authorisation Server into the Management Console, and from there will interact with the user and the agents that the user is permitted to connect to. When SEM scripts are created or modified a single, central, copy is retained at the SEM Authorization Server.


	~~[[File:SEMComponents_Small~~.~~jpg]]~~

Mike.schofield at 14:28, 21 January 2011

2011-01-21T14:28:59Z

← Older revision		Revision as of 14:28, 21 January 2011
Line 8:		Line 8:


	[[File:~~SEMComponents~~.jpg]]		[[File:SEMComponents_Small.jpg]]

Mike.schofield at 14:23, 21 January 2011

2011-01-21T14:23:39Z

← Older revision		Revision as of 14:23, 21 January 2011
Line 8:		Line 8:


	[[File:~~http://www.sysgem.com/WIKI_Images/DevGuide/~~SEMComponents.jpg]]		[[File:SEMComponents.jpg]]

Mike.schofield at 13:18, 21 January 2011

2011-01-21T13:18:37Z

← Older revision		Revision as of 13:18, 21 January 2011
Line 8:		Line 8:


	[[File:~~ftp~~://www.sysgem.com/WIKI_Images/DevGuide/SEMComponents.jpg]]		[[File:http://www.sysgem.com/WIKI_Images/DevGuide/SEMComponents.jpg]]

Mike.schofield at 13:17, 21 January 2011

2011-01-21T13:17:56Z

← Older revision		Revision as of 13:17, 21 January 2011
Line 8:		Line 8:


	[[File:ftp://~~ftp~~.sysgem.com/WIKI_Images/DevGuide/SEMComponents.jpg]]		[[File:ftp://www.sysgem.com/WIKI_Images/DevGuide/SEMComponents.jpg]]

Mike.schofield at 13:15, 21 January 2011

2011-01-21T13:15:32Z

← Older revision		Revision as of 13:15, 21 January 2011
Line 8:		Line 8:


	[[File:ftp://ftp.sysgem.com~~/web~~/WIKI_Images/DevGuide/SEMComponents.jpg]]		[[File:ftp://ftp.sysgem.com/WIKI_Images/DevGuide/SEMComponents.jpg]]