M2Web Installation - Revision history

NeilArmstrong: Added glossary link to Configuration~

2012-10-18T18:44:01Z

Added glossary link to Configuration~

← Older revision		Revision as of 18:44, 18 October 2012
Line 49:		Line 49:
	# ln -s mods-available/suexec.load mods-enabled/		# ln -s mods-available/suexec.load mods-enabled/

	7. Test the apache configuration for errors.		7. Test the apache [[configuration~\|Configuration]] for errors.

	# apache2 -S		# apache2 -S

	8. Restart the apache web server to enable the new configuration.		8. Restart the apache web server to enable the new [[configuration~\|Configuration]].

	# apache2ctl graceful		# apache2ctl graceful

	9. Append vista as an alternate name for 127.0.0.1 in /etc/hosts (for local testing). If your server name is testpc, the configuration line would look something like this:		9. Append vista as an alternate name for 127.0.0.1 in /etc/hosts (for local testing). If your server name is testpc, the [[configuration~\|Configuration]] line would look something like this:

	127.0.0.1 localhost.localdomain localhost testpc vista		127.0.0.1 localhost.localdomain localhost testpc vista
Line 88:		Line 88:


	Note: on my CentOS configuration, apache2 has been renamed to httpd		Note: on my CentOS [[configuration~\|Configuration]], apache2 has been renamed to httpd
	Also note, the "#" at the beginning of each line indicates that the user should be administrator.		Also note, the "#" at the beginning of each line indicates that the user should be administrator.
	su -		su -
Line 106:		Line 106:
	and that all the VistA files were owned by the vista group.		and that all the VistA files were owned by the vista group.

	7. Test the apache configuration for errors.		7. Test the apache [[configuration~\|Configuration]] for errors.

	# httpd -S		# httpd -S

	8. Restart the apache web server to enable the new configuration.		8. Restart the apache web server to enable the new [[configuration~\|Configuration]].

	# /usr/bin/system-config-services		# /usr/bin/system-config-services

NeilArmstrong: Added Glossary Link to Historical~

2012-03-03T00:50:57Z

Added Glossary Link to Historical~

← Older revision		Revision as of 00:50, 3 March 2012
Line 2:		Line 2:


	This page uses the historical meaning of the term "OpenVistA" [[VistA Trademark Issues]]		This page uses the [[historical~\| Historical]] meaning of the term "OpenVistA" [[VistA Trademark Issues]]

	The following page initially copied from:		The following page initially copied from:
Line 18:		Line 18:
	1. download and expand the latest m2web*.tgz file into directory "/usr/local/m2web".		1. download and expand the latest m2web*.tgz file into directory "/usr/local/m2web".

	# mkdir /usr/local/m2web		# mkdir /usr/local/m2web F
	# cd /usr/local/m2web		# cd /usr/local/m2web
	# wget http://vista.vmth.ucdavis.edu/files/m2web_20060519_pre.tgz		# wget http://vista.vmth.ucdavis.edu/files/m2web_20060519_pre.tgz

Ftrotter: trademark

2007-03-07T16:18:07Z

trademark

← Older revision		Revision as of 16:18, 7 March 2007
Line 1:		Line 1:
	Back: [[M2Web Overview]]		Back: [[M2Web Overview]]


			This page uses the historical meaning of the term "OpenVistA" [[VistA Trademark Issues]]

	The following page initially copied from:		The following page initially copied from:

Kdtop at 11:40, 24 October 2006

2006-10-24T11:40:59Z

← Older revision		Revision as of 11:40, 24 October 2006
Line 95:		Line 95:
	6. Enable the vista virtual server in Apache and the suexec module so it can run as user vista.		6. Enable the vista virtual server in Apache and the suexec module so it can run as user vista.

	I don't know how to do this on my system, and it seems to run without it. This susexec module allows Apache to operate as a different user. I don't need this because I specify:		I don't know how to do this on my system, and it seems to run without it.
	User apache		This susexec module allows Apache to operate as a different user.
	Group vista		I don't need this because I specify:
	And then I made sure that the apache user was a member of the vista group, and that all the VistA files were owned by the vista group.		User apache
			Group vista
			And then I made sure that the apache user was a member of the vista group,
			and that all the VistA files were owned by the vista group.

	7. Test the apache configuration for errors.		7. Test the apache configuration for errors.

Kdtop at 11:40, 24 October 2006

2006-10-24T11:40:04Z

← Older revision		Revision as of 11:40, 24 October 2006
Line 95:		Line 95:
	6. Enable the vista virtual server in Apache and the suexec module so it can run as user vista.		6. Enable the vista virtual server in Apache and the suexec module so it can run as user vista.

	I don't know how to do this on my system, and it seems to run without it.		I don't know how to do this on my system, and it seems to run without it. This susexec module allows Apache to operate as a different user. I don't need this because I specify:
			User apache
			Group vista
			And then I made sure that the apache user was a member of the vista group, and that all the VistA files were owned by the vista group.

	7. Test the apache configuration for errors.		7. Test the apache configuration for errors.

Kdtop at 11:36, 24 October 2006

2006-10-24T11:36:25Z

← Older revision		Revision as of 11:36, 24 October 2006
Line 78:		Line 78:
	'''Kevin's modifications of above'''		'''Kevin's modifications of above'''

	One of the most important issues with installing M2web (and the problem that took me a few days to figure out) is linux file permissions. M2web will probably be running as a different user that one normally uses to run VistA. An unless permissions are set properly, the Apache web server will be able to access the needed VistA files.		One of the most important issues with installing M2web (and the problem that took me a few days to figure out) is linux file permissions. M2web will probably be running as a different user that one normally uses to run VistA. An unless permissions are set properly, the Apache web server will not be able to access the needed VistA files.

	The way I finally solved this problem, following Jim Self's advice, was to ensure that the apache user was a member of the vista group. This may be different on your setup. Find out what group your VistA files belong to, and then add the apache user to this group. There should be tutorials on the web for determining group ownership for files, and for adding users to groups. This is linux level stuff.		The way I finally solved this problem, following Jim Self's advice, was to ensure that the apache user was a member of the vista group. This may be different on your setup. Find out what group your VistA files belong to, and then add the apache user to this group. There should be tutorials on the web for determining group ownership for files, and for adding users to groups. This is linux level stuff.

Kdtop at 11:35, 24 October 2006

2006-10-24T11:35:55Z

← Older revision		Revision as of 11:35, 24 October 2006
Line 77:		Line 77:

	'''Kevin's modifications of above'''		'''Kevin's modifications of above'''

			One of the most important issues with installing M2web (and the problem that took me a few days to figure out) is linux file permissions. M2web will probably be running as a different user that one normally uses to run VistA. An unless permissions are set properly, the Apache web server will be able to access the needed VistA files.

			The way I finally solved this problem, following Jim Self's advice, was to ensure that the apache user was a member of the vista group. This may be different on your setup. Find out what group your VistA files belong to, and then add the apache user to this group. There should be tutorials on the web for determining group ownership for files, and for adding users to groups. This is linux level stuff.

			---


	Note: on my CentOS configuration, apache2 has been renamed to httpd		Note: on my CentOS configuration, apache2 has been renamed to httpd

Kdtop at 20:44, 14 October 2006

2006-10-14T20:44:57Z

← Older revision		Revision as of 20:44, 14 October 2006
Line 98:		Line 98:
	# /usr/bin/system-config-services		# /usr/bin/system-config-services
	In this GUI, find and highlight httpd and press [restart] buttion		In this GUI, find and highlight httpd and press [restart] buttion

			or try
			# httpd -k restart

Kdtop at 19:53, 14 October 2006

2006-10-14T19:53:31Z

← Older revision		Revision as of 19:53, 14 October 2006
Line 9:		Line 9:

	========================================		========================================
	M2Web setup update 2006-05-19 by Jim Self		'''M2Web setup update 2006-05-19 by Jim Self'''

	The setup of M2Web on Debian with OpenVistA is pretty simple now if OpenVistA and Apache2 are already installed. I assume that OpenVista files are owned by user vista and installed in directory /usr/local/vista/OpenVistA/ and that M2Web files will be owned by user m2web and installed in /usr/local/m2web/. For a private or a demonstration server, M2Web files could as well be installed in the same place and with the same owner as for OpenVistA.		The setup of M2Web on Debian with OpenVistA is pretty simple now if OpenVistA and Apache2 are already installed. I assume that OpenVista files are owned by user vista and installed in directory /usr/local/vista/OpenVistA/ and that M2Web files will be owned by user m2web and installed in /usr/local/m2web/. For a private or a demonstration server, M2Web files could as well be installed in the same place and with the same owner as for OpenVistA.

Kdtop at 19:53, 14 October 2006

2006-10-14T19:53:11Z

← Older revision		Revision as of 19:53, 14 October 2006
Line 76:		Line 76:
	========================================		========================================

	Kevin's modifications of above.		'''Kevin's modifications of above'''

	Note: on my CentOS configuration, apache2 has been renamed to httpd		Note: on my CentOS configuration, apache2 has been renamed to httpd
			Also note, the "#" at the beginning of each line indicates that the user should be administrator.
			su -
			enter password: <--- enter password
			# <-- now in super user mode

	5. edit m2web-vista-site to match your installation. Then copy this file and append it to your httpd.conf file. Here is how my final httpd.conf looks: [[KT's httpd.conf]]		5. edit m2web-vista-site to match your installation. Then copy this file and append it to your httpd.conf file. Here is how my final httpd.conf looks: [[KT's httpd.conf]]