Changes between Version 53 and Version 54 of Old/hNodes/cNodeVer3/dAssembly/e4NodesSetup

Timestamp:

Jun 24, 2013, 9:13:27 PM (12 years ago)

Author:

ParviK

Comment:

—

Old/hNodes/cNodeVer3/dAssembly/e4NodesSetup

@@ -161 +161 @@
 ====== Setting up XMPP service ======
 
-In the /etc/java-6-openjdk/security/java.security file, comment out the following line:
-{{{
-security.provider.9=sun.security.pkcs11.SunPKCS11 ${java.home}/lib/security/nss.cfg
-}}}
+1. In the /etc/java-6-openjdk/security/java.security file, comment out the following line:
+ {{{ 
+   security.provider.9=sun.security.pkcs11.SunPKCS11 ${java.home}/lib/security/nss.cfg
+ }}}
+2. Open /etc/init.d/openfire file in an editor and modify line 27 to point to the correct java directory. In our case, it is /usr/lib/jvm/java-6-openjdk.
+
+3. Start openfire using command 
+{{{
+  /etc/init.d/openfire start
+}}} 
+4. Check if openfire is running: ps aux | grep openfire . Startup can take a while, please be patient. 
+
+5. Direct your web browser to http://localhost:9090 and begin the setup wizard. If you are unable to connect to http://localhost:9090, then do the following: 
+
+6. Choose your language and click continue
+
+7. Enter the AM's hostname in the Domain field and click continue
+
+8. Choose the embedded database and continue. 
+
+9. Choose the default profile and click continue
+
+10. Enter an admin password and click continue, then wait until the installation is finished. In most cases, the username and password is 'admin'.
+
 
 ====== Setting up CMC service ======
@@ -246 +266 @@
 ====== Setting up Login Service ======
 
-* From exernal1, get ogs_scheduler from /usr/share/omf-aggmgr-5.4/omf-aggmgr and scheduler.yaml from /etc/omf-aggmgr-5.4/enabled and save it to /usr/share/omf-aggmgr-5.4/omf-aggmgr and /etc/omf-aggmgr-5.4/available,respectively, on your console.
+* From exernal1, get ogs_scheduler from /usr/share/omf-aggmgr-5.4/omf-aggmgr and scheduler.yaml from /etc/omf-aggmgr-5.4/enabled and save it to /usr/share/omf-aggmgr-5.4/omf-aggmgr and /etc/omf-aggmgr-5.4/available,respectively, on your console. Follow the steps given below to setup the scheduler.
+
+    * ''' Configuring apache web server '''
+
+       1. In the following we are assuming that <host> is the internal hostname or IP address of the machine running the login AM, and <port> is the IP port on which the service is running (default is 5052 for OMF 5.2services). For example, forn internal IP 172.16.250.7 and port 5025 the <host>:<port> would be: 172.16.250.7:5052.
+
+  ServerName <server_name>
+  {{{
+
+   ProxyPass /status "http://<host>:<port>/public_html/"
+    <Location /status>
+      Order allow,deny
+      Allow from all
+    </Location>
+
+  ProxyPass /userManagement "http://<host>:<port>/login/userManagement"
+  <Location /userManagement>
+    Order allow,deny
+    Allow from all
+  </Location>
+
+  }}}
+
+       Note: If you change baseURL and publicURL in login.yaml it is necessary to change corresponding values in apache default file.
+
+       2. For SSL services (in /etc/apache2/sites-available/default-ssl) we need:
+
+       {{{
+          ProxyPass /schedule/  "http://<host>:<port>/login/ShowScheduler" 
+          <Location /schedule >
+          Order allow,deny
+          Allow from all
+          </Location>
+
+          ProxyPass /loginService/  http://<host>:<port>/login/
+          <Location  /loginService>
+          AllowOverride None
+          order allow,deny
+          allow from all
+          </Location>
+          <Proxy http://<host>:<port>/login/*>
+          AllowOverride None
+          order allow,deny
+          allow from all
+          </Proxy>
+       }}}
 
 * From internal2, get ogs_login from /usr/share/omf-aggmgr-5.4/omf-aggmgr and login.yaml from /etc/omf-aggmgr-5.4/enabled and save it to /usr/share/omf-aggmgr-5.4/omf-aggmgr and /etc/omf-aggmgr-5.4/available,respectively, on your console.
@@ -252 +317 @@
 * Modify login.yaml and scheduler.yaml according to your testbed.
    
+
 ''' Setting up LDAP client '''
 
@@ -396 +462 @@
    ldapsearch -x localhost -D "cn=admin,dc=orbit-=lab,dc=org" -W -b "dc=orbit-lab,dc=org" uid=*
 }}}
-
-
-====== Configuring apache web server ======
-
-1. 
-In the following we are assuming that <host> is the internal hostname or IP address of the machine running the login AM, and <port> is the IP port on which the service is running (default is 5052 for OMF 5.2 services). For example, forn internal IP 172.16.250.7 and port 5025 the <host>:<port> would be: 172.16.250.7:5052.
-
-ServerName <server_name>
-{{{
-
- ProxyPass /status "http://<host>:<port>/public_html/"
-  <Location /status>
-    Order allow,deny
-    Allow from all
-  </Location>
-
-  ProxyPass /userManagement "http://<host>:<port>/login/userManagement"
-  <Location /userManagement>
-    Order allow,deny
-    Allow from all
-  </Location>
-
-}}}
-
-Note: If you change baseURL and publicURL in login.yaml it is necessary to change corresponding values in apache default file.
-
-2. For SSL services (in /etc/apache2/sites-available/default-ssl) we need:
-
-{{{
-  ProxyPass /schedule/  "http://<host>:<port>/login/ShowScheduler"
-  <Location /schedule>
-    Order allow,deny
-    Allow from all
-  </Location>
-
-  ProxyPass /loginService/  http://<host>:<port>/login/
-  <Location  /loginService>
-     AllowOverride None
-     order allow,deny
-     allow from all
-  </Location>
-  <Proxy http://<host>:<port>/login/*>
-     AllowOverride None
-     order allow,deny
-     allow from all
-   </Proxy>
-}}}