OS4X administrative interface - Revision history

Admin at 10:36, 26 February 2014

2014-02-26T10:36:14Z

2013-11-26T07:58:31Z

2013-11-26T07:57:22Z

2013-11-26T07:53:42Z

2013-04-26T12:18:35Z

OS4X admin interface app

2013-04-26T11:44:50Z

2013-04-26T11:38:11Z

OS4X admin interface app

2013-04-26T11:37:41Z

OS4X admin interface app

2013-04-26T11:23:23Z

OS4X admin interface app

2013-04-26T11:23:13Z

OS4X admin interface app

← Older revision		Revision as of 10:36, 26 February 2014
Line 9:		Line 9:
	http://os4x-server/os4x/		http://os4x-server/os4x/
	from where on the interface dynamically forwards the user to the correct directory.		from where on the interface dynamically forwards the user to the correct directory.
−
−	~~=== Server selection in the web interface ===~~
−	As a feature available since 2013-04-26, the admninistrative web interface can communicate with any other OS4Xapi instances than the local one (single requirement: the OS4Xapi you are communicating with must be of at least the same version). You can access the selection on different ways:
−	*Use the menu to select the entry "Configuration" -> "Switch OS4X srv.":
−	~~[[Image:Os4xadmin select server.png]]~~
−	*Navigate to any OS4X administrative interface and add the appendix "<code>?server</code>":
−	~~http://localhost/os4x/?server~~
−
−	The shown interface asks you where your OS4Xapi is located to which you want to communicate. In most common installations, you can enter the URL of the administrative webinterface (i.e. '<code>http://os4x-server/os4x</code>'):
−
−	~~[[Image:Os4x admin serversel empty.png]]~~
−
−	~~After a valid OS4Xapi has been found, the interface dynamically displays a popup which indicates that a URL was entered (and can be used) which is a valid OS4Xapi URL.~~
−
−	~~[[Image:Os4x admin serversel ok.png]]~~

← Older revision		Revision as of 07:58, 26 November 2013
Line 18:		Line 18:

	The shown interface asks you where your OS4Xapi is located to which you want to communicate. In most common installations, you can enter the URL of the administrative webinterface (i.e. '<code>http://os4x-server/os4x</code>'):		The shown interface asks you where your OS4Xapi is located to which you want to communicate. In most common installations, you can enter the URL of the administrative webinterface (i.e. '<code>http://os4x-server/os4x</code>'):
		+
		+	[[Image:Os4x admin serversel empty.png]]
		+
		+	After a valid OS4Xapi has been found, the interface dynamically displays a popup which indicates that a URL was entered (and can be used) which is a valid OS4Xapi URL.
		+
		+	[[Image:Os4x admin serversel ok.png]]

← Older revision		Revision as of 07:57, 26 November 2013
Line 18:		Line 18:

	The shown interface asks you where your OS4Xapi is located to which you want to communicate. In most common installations, you can enter the URL of the administrative webinterface (i.e. '<code>http://os4x-server/os4x</code>'):		The shown interface asks you where your OS4Xapi is located to which you want to communicate. In most common installations, you can enter the URL of the administrative webinterface (i.e. '<code>http://os4x-server/os4x</code>'):
−
−	~~[[Image:Os4x admin serversel empty.png]]~~
−
−	~~After a valid OS4Xapi has been found, the interface dynamically displays a popup which indicates that a URL was entered (and can be used) which is a valid OS4Xapi URL.~~
−
−	~~[[Image:Os4x admin serversel ok.png]]~~

← Older revision		Revision as of 07:53, 26 November 2013
Line 24:		Line 24:

	[[Image:Os4x admin serversel ok.png]]		[[Image:Os4x admin serversel ok.png]]
−
−	~~== OS4X admin interface app ==~~
−	~~[[Image:OS4Xadmin exe.png]] [[Image:OS4Xadmin mac.png]]~~
−
−	In situations where your local webbrowser is horrible slow (i.e. using Internet Explorer), you can use the native OS4X admin interface as a richt-client application. The native application offers the same functionality as the administrative web interface. You have to know where your OS4Xapi is reachable via http(s) you want to communicate with. The contacted OS4Xapi must be at least the release of 2013-04-26.
−
−	~~=== Optional parameters ===~~
−	You can pass as a single first parameter the URL of the OS4Xapi to the program when starting. This URL will be used for the communication between the frontend and backend. If the URL doesn't point to a valid OS4Xapi, the GUI will not start with the given OS4Xapi, but shows you the start screen with the input field for the OS4Xapi URL (same as started without any parameter.
−
−	~~Example:~~
−	~~C:\Program Files (x86)\OS4Xadmin>"OS4X administrative interface.exe" http://192.168.1.70~~

@@ Line 28: / Line 28: @@
 [[Image:OS4Xadmin exe.png]] [[Image:OS4Xadmin mac.png]]
-In situations where your local webbrowser is horrible slow (i.e. using Internet Explorer), you can use the native OS4X admin interface as a richt-client application. The native application offers the same functionality as the administrative web interface. You have to know where your OS4Xapi is reachable via http(s) you want to communicate with.
+In situations where your local webbrowser is horrible slow (i.e. using Internet Explorer), you can use the native OS4X admin interface as a richt-client application. The native application offers the same functionality as the administrative web interface. You have to know where your OS4Xapi is reachable via http(s) you want to communicate with. The contacted OS4Xapi must be at least the release of 2013-04-26.
 === Optional parameters ===

@@ Line 1: / Line 1: @@
 The administrative interface of OS4X is available in different versions. The most common one is the web interface, which is accessed via a webbrowser of your choice.
@@ Line 6: / Line 4: @@
 == OS4X administrative web interface ==
 The most easy way of accessing the administrative interface is by using the web interface. Its standard installation directory gives the administrator access via an URL like
   http://os4x-server/os4x/

@@ Line 26: / Line 26: @@
 == OS4X admin interface app ==
-[[Image:OS4Xadmin exe.png]]
+[[Image:OS4Xadmin exe.png]] [[Image:OS4Xadmin mac.png]]
 In situations where your local webbrowser is horrible slow (i.e. using Internet Explorer), you can use the OS4X admin interface as a richt-client application. The application offers the same functionality as the administrative web interface. You have to know where your OS4Xapi is reachable via http(s) you want to communicate with.

← Older revision		Revision as of 11:23, 26 April 2013
Line 26:		Line 26:

	== OS4X admin interface app ==		== OS4X admin interface app ==
		+	[[Image:OS4Xadmin exe.png]]
	In situations where your local webbrowser is horrible slow (i.e. using Internet Explorer), you can use the OS4X admin interface as a richt-client application. The application offers the same functionality as the administrative web interface. You have to know where your OS4Xapi is reachable via http(s) you want to communicate with.		In situations where your local webbrowser is horrible slow (i.e. using Internet Explorer), you can use the OS4X admin interface as a richt-client application. The application offers the same functionality as the administrative web interface. You have to know where your OS4Xapi is reachable via http(s) you want to communicate with.