Author: fapeeler
Date: Thu Oct 11 19:52:06 2012
New Revision: 1397268
URL: http://svn.apache.org/viewvc?rev=1397268&view=rev
Log:
CMS commit to vcl by fapeeler
Modified:
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext
Modified:
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext
URL:
http://svn.apache.org/viewvc/vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext?rev=1397268&r1=1397267&r2=1397268&view=diff
==============================================================================
---
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext
(original)
+++
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext
Thu Oct 11 19:52:06 2012
@@ -40,27 +40,28 @@ This page provides information on how to
# Shutdown services #
Shutdown the httpd and vcld services
+
- :::BashLexer
- service httpd stop or /etc/init.d/httpd stop
- service vcld stop or /etc/init.d/vcld stop
+ :::BashLexer
+ service httpd stop or /etc/init.d/httpd stop
+ service vcld stop or /etc/init.d/vcld stop
# Create a backup of vcl database #
We will create a backup of the vcl database. This will provide a restore point
if necessary.
- :::BashLexer
- mysqldump vcl > ~/vcl-pre2.3-upgrade.sql
+ :::BashLexer
+ mysqldump vcl > ~/vcl-pre2.3-upgrade.sql
# Update mysql schema #
This step updates the mysql schema.
- :::BashLexer
- cd /root/apache-VCL-2.3
- mysql vcl < mysql/update-vcl.sql
+ :::BashLexer
+ cd /root/apache-VCL-2.3
+ mysql vcl < mysql/update-vcl.sql
- **Note**: A new resource group is added in update-vcl.sql - **all
profiles**. Access to manage the group is added to the VCL->admin node in the
privilege tree if that node exists. If not, you will need to add it manually
after starting httpd again. To add it manually, pick a node in the privilege
tree, scroll to Resources, click Add Resource Group, select serverprofile/all
profiles from the drop-down box, check available, administer, manageGroup, and
manageMapping, and click Submit New Resource Group.
+**Note**: A new resource group is added in update-vcl.sql - **all profiles**.
Access to manage the group is added to the VCL->admin node in the privilege
tree if that node exists. If not, you will need to add it manually after
starting httpd again. To add it manually, pick a node in the privilege tree,
scroll to Resources, click Add Resource Group, select serverprofile/all
profiles from the drop-down box, check available, administer, manageGroup, and
manageMapping, and click Submit New Resource Group.
# Update web code #
@@ -68,61 +69,61 @@ This step we will move the 2.2.1 web dir
1. move your old code out of the way
- :::BashLexer
- cd /var/www/html
- mv vcl ~/vcl_2.2.1_web
+ :::BashLexer
+ cd /var/www/html
+ mv vcl ~/vcl_2.2.1_web
2. copy the new code in place
- :::BashLexer
- cd /root/apache-VCL-2.3
- cp -r web /var/www/html/vcl
+ :::BashLexer
+ cd /root/apache-VCL-2.3
+ cp -r web /var/www/html/vcl
3. copy your 2.2.1 config files
- :::BashLexer
- cd ~/vcl_2.2.1_web/.ht-inc
- cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc
+ :::BashLexer
+ cd ~/vcl_2.2.1_web/.ht-inc
+ cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc
4. Make the maintenance directory writable by the web server user. You will
need to know what user httpd runs as on your server. This can be found with
- :::BashLexer
- ps aux | grep httpd
+ :::BashLexer
+ ps aux | grep httpd
Look at the first column. One process will be owned by root. The remaining
processes will be owned by the web server user. Now, own
/var/www/html/vcl/.ht-inc/maintenance to that user (replacing 'apache' with
your web server user if different):
- :::BashLexer
- chown apache /var/www/html/vcl/.ht-inc/maintenance
+ :::BashLexer
+ chown apache /var/www/html/vcl/.ht-inc/maintenance
5. make some changes to conf.php:
- a. A new user group permission that controls who can manage block allocations
globally or for a specific affiliation has been added. It can be granted to any
user group under Privileges->Additional User Permissions->Manage Block
Allocations. Users with this permission are notified of new block allocation
requests. Remove
+ a. A new user group permission that controls who can manage block
allocations globally or for a specific affiliation has been added. It can be
granted to any user group under Privileges->Additional User Permissions->Manage
Block Allocations. Users with this permission are notified of new block
allocation requests. Remove
:::BashLexer
$blockNotifyUsers
from conf.php.
- b. A new user group permission that controls who can look up users globally
or for a specific affiliation has been added. It can be granted to any user
group under Privileges->Additional User Permissions->User Lookup. Users with
this permission can look up information about other users. Remove
+ b. A new user group permission that controls who can look up users
globally or for a specific affiliation has been added. It can be granted to any
user group under Privileges->Additional User Permissions->User Lookup. Users
with this permission can look up information about other users. Remove
:::BashLexer
$userlookupUsers
- c. Multilingualization has been added VCL. So, DEFAULTLOCALE has been added
to conf.php to set the default locale. Add
+ c. Multilingualization has been added VCL. So, DEFAULTLOCALE has been
added to conf.php to set the default locale. Add
- :::BashLexer
- define("DEFAULTLOCALE", "en_US");
+ :::BashLexer
+ define("DEFAULTLOCALE", "en_US");
to conf.php, changing en_US if needed to match your locale. You can look in
/var/www/html/vcl/locale to see which ones are available.
- d. Users authenticated using Shibboleth without also having an LDAP server
can now be added before they log in. Add
+ d. Users authenticated using Shibboleth without also having an LDAP server
can now be added before they log in. Add
- :::BashLexer
- define("ALLOWADDSHIBUSERS", 0);
+ :::BashLexer
+ define("ALLOWADDSHIBUSERS", 0);
to conf.php. If you are using Shibboleth and would like to be able to add
users to groups before the user has ever logged in to VCL, you can set this to
1. However, please note that if you typo the userid, there is no way to verify
it, and the user will be added with the typoed userid.
- e. Some LDAP related items have been simplified in the code using some
additional options in $authMechs. For any LDAP entries, you need to add two
options. "lookupuserbeforeauth" is used if you need VCL to look up the full DN
of a user and use that when doing the bind that authenticates the user (if you
don't know what this means, leave it set to 0). If you need to set it to 1,
then you will need to set "lookupuserfield" to what LDAP attribute to use when
looking up the user's DN (typically either 'cn', 'uid', or 'samaccountname').
Add
+ e. Some LDAP related items have been simplified in the code using some
additional options in $authMechs. For any LDAP entries, you need to add two
options. "lookupuserbeforeauth" is used if you need VCL to look up the full DN
of a user and use that when doing the bind that authenticates the user (if you
don't know what this means, leave it set to 0). If you need to set it to 1,
then you will need to set "lookupuserfield" to what LDAP attribute to use when
looking up the user's DN (typically either 'cn', 'uid', or 'samaccountname').
Add
:::BashLexer
"lookupuserbeforeauth" => 0,
@@ -130,7 +131,7 @@ This step we will move the 2.2.1 web dir
to each LDAP array you have in the $authMech array in conf.php.
- f. If you are using any Local accounts for authentication, you need to modify
the entries for $addUserFunc and $updateUserFunc. Change
+ f. If you are using any Local accounts for authentication, you need to
modify the entries for $addUserFunc and $updateUserFunc. Change
:::BashLexer
$addUserFunc[$item['affiliationid']] = create_function('', 'return
0;');
@@ -143,8 +144,8 @@ This step we will move the 2.2.1 web dir
# Restart httpd service #
- :::BashLexer
- service httpd start or /etc/init.d/httpd start
+ :::BashLexer
+ service httpd start or /etc/init.d/httpd start
# Update management node code #
