Base Software Installation

Nick — Mon, 06 Sep 2010 07:09:27 GMT

Required Packages:

←Older revision		Revision as of 07:09, 6 September 2010
(One intermediate revision not shown.)
Line 12:		Line 12:
	=== Fedora 9 ===		=== Fedora 9 ===

-	It is assumed you're experienced with installing Fedora 9 onto a system. If this is beyond your abilities.. or you struggle with it.... cough	+	It is assumed you're experienced with installing Fedora 9 onto a system.
-		+
-	~~Moving on..~~.	+

	Install Fedora 9 x64 with minimal packages. I choose to install and uncheck every package in the GUI installer except OpenSSH server and client, and YUM.		Install Fedora 9 x64 with minimal packages. I choose to install and uncheck every package in the GUI installer except OpenSSH server and client, and YUM.
Line 35:		Line 33:
	<blockquote class="snixblockquote">		<blockquote class="snixblockquote">
	<span style="color: blue">		<span style="color: blue">
-	yum -y install which compat-libstdc++-33 compat-libstdc++-296 ntp libXext unzip perl xdpyinfo uuid xinetd ksh ntp tcsh rsync gettext unzip	+	yum -y install which compat-libstdc++-33 compat-libstdc++-296 ntp libXext unzip perl xdpyinfo uuid xinetd ksh ntp tcsh rsync gettext unzip libXtst.i386 libXi.i386 libxml2.i386 nss.i386 zlib.i386 libXext.i386 uuid.i386 e2fsprogs-libs.i386 gettext.i386 compat-libstdc++-33.i386 glibc-2.8-8.i386 pam.i386
-	~~</span>~~	+
-	~~</blockquote>~~	+
-		+
-	~~<blockquote class="snixblockquote">~~	+
-	~~<span style="color: blue">~~	+
-	~~yum -y install~~ libXtst.i386 libXi.i386 libxml2.i386 nss.i386 zlib.i386 libXext.i386 uuid.i386 e2fsprogs-libs.i386 gettext.i386 compat-libstdc++-33.i386 glibc-2.8-8.i386 pam.i386	+
	</span>		</span>
	</blockquote>		</blockquote>

Sun Java Calendar Server 7

Nick — Mon, 06 Sep 2010 03:27:15 GMT

Access Manager 7.1:

New page

{{Site Settings}}

== Basic System Hardware Recommendations ==
Sun recommends the following for the basic hardware configuration:
* RAM: 4gig
* SWAP: 4gig

Pretty much everything else is up to you. Of course, quick disk (RAID) is very handy! ^^

== Basic System Configuration ==

=== Fedora 13 ===

It is assumed you're experienced with installing Fedora 13 onto a system.

Install Fedora 13 x64 with minimal packages. I choose to install and uncheck every package in the GUI installer except OpenSSH server and client, and YUM.

Make sure your HOSTNAME is a FQDN:

<blockquote class="snixblockquote">
hostname {{#var:hostname}}
</blockquote>

If it's not a FQDN, change the ''/etc/sysconfig/network'' file (probably should reboot after this)

=== Required Packages ===

After lots of trial and error, the following packages were found to be required in order to be able to run the Sun Java software on Fedora 13 x64.

Install the following packages using this command:

<blockquote class="snixblockquote">

yum -y install which compat-libstdc++-33 compat-libstdc++-296 ntp libXext unzip perl xdpyinfo uuid xinetd ksh ntp tcsh rsync gettext unzip libXtst.i686 libXi.i686 libxml2.i686 nss.i686 zlib.i686 libXext.i686 uuid.i686 e2fsprogs-libs.i686 gettext.i686 compat-libstdc++-33.i686 glibc-2.8-8.i686 pam.i686 libuuid.i686 libuuid libXtst.i686

</blockquote>

Note the ''.i686'' packages are required for compatibility when running Fedora 13 x64

=== System Tuning Changes ===

Sun recommends the following:

Edit the /etc/sysctl.conf "tuning" file and add:

<blockquote class="snixblockquote">
fs.file-max = 16384 
net.ipv4.tcp_tw_reuse = 1 
net.ipv4.tcp_tw_recycle = 1 
net.core.wmem_max = 8388608 
net.core.rmem_max = 8388608 
net.ipv4.tcp_rmem = 4096 87380 8388608 
net.ipv4.tcp_wmem = 4096 87380 8388608 
net.ipv4.ip_local_port_range = 1024 65536 
net.ipv4.tcp_fin_timeout = 30 
</blockquote>

=== System Environment Changes ===

In order to be able to run the X11 installer for some of the Sun packages, we need to make a link to the directory that the installer checks for before it will start a X window:

<blockquote class="snixblockquote">
mkdir /usr/X11R6; ln -s /usr/bin /usr/X11R6/bin
</blockquote>

== Software Installation ==

''Note: This assumes you already have downloaded all the Sun packages to your local system''

=== Directory Server Enterprise Edition 6.3 ===

''Ref: [http://docs.sun.com/app/docs/doc/820-2761/install-dsee-zip?a=view Install DSEE 6.3 from Zip]''

Unpack the ZIP archive into a temporary directory and launch the installer:

<blockquote class="snixblockquote">
mkdir DSEE6.3 
cd DSEE6.3 
tar zxBf ../DSEE.6.3.Linux-X86-full.tar.gz 
cd DSEE_ZIP_Distribution 
./dsee_deploy install -i {{#var:directory_server_root}} 
</blockquote>

Wade through the lengthy license agreement... and wait for the install complete.

Next, we need to create a directory for our new LDAP server instance:

<blockquote class="snixblockquote">
mkdir -p {{#var:directory_server_data}}/
</blockquote>

And finally, create the instance in the directory.:

<blockquote class="snixblockquote">
{{#var:directory_server_root}}/ds6/bin/dsadm create -p {{#var:directory_server_port}} {{#var:directory_server_data}}/{{#var:directory_server_instance_name}} 
Choose the Directory Manager password: '''{{#var:directory_manager_dn_pass}}''' 
Confirm the Directory Manager password: '''{{#var:directory_manager_dn_pass}}''' 
Use 'dsadm start '{{#var:directory_server_data}}/{{#var:directory_server_instance_name}}'' to start the instance 
</blockquote>

Copy the libcrypt.so.1 from a Fedora 9 x32 or Fedora 9 x64 with the glibc.i386 packages installed into the Sun DSEE library directory /opt/sun/directory/ds6/lib

Start the instance up like the create command tells you:

<blockquote class="snixblockquote">
{{#var:directory_server_root}}/ds6/bin/dsadm start {{#var:directory_server_data}}/{{#var:directory_server_instance_name}}
</blockquote>

And lastly, create a suffix for this instance:

<blockquote class="snixblockquote">
{{#var:directory_server_root}}/ds6/bin/dsconf create-suffix -h {{#var:directory_server_host}} -p {{#var:directory_server_port}} {{#var:ldap_root_suffix}} 
Certificate "CN={{#var:hostname}}, CN=636, CN=Directory Server, O=Sun Microsystems" presented by the server is not trusted. 
Type "Y" to accept, "y" to accept just once, "n" to refuse, "d" for more details: '''Y''' 
Enter "cn=Directory Manager" password: '''{{#var:directory_manager_dn_pass}}''' 
</blockquote>

Make sure to answer the Certificate question with a CAPITAL '''Y''' or you'll be prompted to accept the certificate over again

That's it. The DSEE 6.3 installation is very straightforward and simple compared to the rest of the installs!

==== CACAO ====

TODO: make sure CACAO is running:
/opt/sun/directory/dsee6/cacao_2/cacao/bin/cacaoadm start

=== Sun GlassFish Enterprise Server with HADB v2.1 patch 02 ===

Make sure you have installed a 32-bit Sun Java SDK or JRE with JAVA_HOME set correctly, the installer will not run with the bundled Java JRE or a 64-bit JRE.

Set the install package as "executable" and then run it: (make sure to set your X11 'DISPLAY' environment variable or you'll get the text mode installer)

chmod +x sges_ee-2_1-p02-linux.bin
./sges_ee-2_1-p02-linux.bin {{#var:console}}

You should see a bunch of installer messages pop up:
Checking available disk space...
Checking Java(TM) 2 Runtime Environment...
Extracting Java(TM) 2 Runtime Environment files...
Extracting installation files...
Launching Java(TM) 2 Runtime Environment...
...

And choose the installation directory. Place the application server into '''{{#var:app_server_root}}''':

Let the installer create the directory:

Now uncheck the '''Sample Applications'''.. Your should only be installing the '''Node Agent''' and '''Domain Administration Server and Administration Tool''':

Use existing Java 2 SDK:

Enter the admin account details and the "master password" - we will end up deleting this instance shortly, so in reality it doesn't matter much what ports you choose here. Just make sure your master password is the one you want:

App Server Admin User: '''{{#var:app_server_domain1_admin_user}}''' 
App Server Admin Pass: '''{{#var:app_server_domain1_admin_pass}}''' 
App Server Master Pass: '''{{#var:app_server_master_password}}''' 
App Server Admin Port: '''{{#var:app_server_admin_port}}''' 
App Server HTTP Port: '''{{#var:app_server_domain1_http_port}}''' 
App Server HTTPs Port: '''{{#var:app_server_domain1_https_port}}''' 

Next, uncheck the '''Enable Updatecenter Client''' since we don't need it:

The installer will perform a disk check and finally display a "Install Now" page:

Hit "Install Now" and let the install do it's thing. Once it's done, you'll be invited to register. Choose '''Skip Registration''' and hit '''next'''.. followed by '''finish''' on the next page to end the installation.

==== Rebuild The Domain ====

The Appserver forces you to enter a username/password and the master password for ''*every*'' startup unless you create the domain with a specific flag to store the credentials for un-prompted startup later. In order to set this up, we need to delete the domain that was created by the installer:

First, set the admin password into a password file:

<blockquote class="snixblockquote">
echo "AS_ADMIN_password={{#var:app_server_domain1_admin_pass}}" > {{#var:app_server_root}}/passwordfile.txt
</blockquote>

Copy the libcrypt.so.1 from a Fedora 9 x32 or Fedora 9 x64 with the glibc.i386 packages installed into the Sun DSEE library directory /opt/sun/appserver/lib

===== Delete the node agent and the node agent config =====

Delete the node-agent:

<blockquote class="snixblockquote">
{{#var:app_server_root}}/bin/asadmin delete-node-agent {{#var:hostname}} 
Command delete-node-agent executed successfully.
</blockquote>

Delete the domain:

<blockquote class="snixblockquote">
rm -rf /opt/sun/appserver/domains/domain1
</blockquote>

===== Create the domain =====

<blockquote style="padding: 1em; margin: 0 0 1.4em 1em; width: auto; background: #f9f9f9; border: 1px dashed #2f6fab; color: black; padding: 1em; line-height: 1.3em;">
{{#var:app_server_root}}/bin/asadmin create-domain --adminport={{#var:app_server_admin_port}} --user={{#var:app_server_domain1_admin_user}} --savemasterpassword=true --instanceport={{#var:app_server_domain1_http_port}} --savelogin=true --domainproperties http.ssl.port={{#var:app_server_domain1_https_port}} {{#var:app_server_default_domain}} 
Please enter the admin password> '''{{#var:app_server_domain1_admin_pass}}''' 
Please enter the admin password again> '''{{#var:app_server_domain1_admin_pass}}''' 
Please enter the master password [Enter to accept the default]:> '''{{#var:app_server_master_password}}''' 
Please enter the master password again [Enter to accept the default]:> '''{{#var:app_server_master_password}}''' 
Using port 4848 for Admin. 
Using port 80 for HTTP Instance. 
Using default port 7676 for JMS. 
Using default port 3700 for IIOP. 
Using port 443 for HTTP_SSL. 
Using default port 3820 for IIOP_SSL. 
Using default port 3920 for IIOP_MUTUALAUTH. 
Using default port 8686 for JMX_ADMIN. 
On Unix platform, port numbers below 1024 may require special privileges. 
Domain being created with profile:enterprise, as specified by variable AS_ADMIN_PROFILE in configuration file. 
Security Store uses: NSS 
Domain {{#var:app_server_default_domain}} created. 
Login information relevant to admin user name [admin] for this domain [{{#var:app_server_default_domain}}] stored at [/root/.asadminpass] successfully. 
Make sure that this file remains protected. Information stored in this file will be used by asadmin commands to manage this domain. 
</blockquote>

===== Start the domain =====

<blockquote style="padding: 1em; margin: 0 0 1.4em 1em; width: auto; background: #f9f9f9; border: 1px dashed #2f6fab; color: black; padding: 1em; line-height: 1.3em;">
{{#var:app_server_root}}/bin/asadmin start-domain --user={{#var:app_server_domain1_admin_user}} --passwordfile={{#var:app_server_root}}/passwordfile.txt {{#var:app_server_default_domain}} 
Starting Domain {{#var:app_server_default_domain}}, please wait. 
Log redirected to {{#var:app_server_domain1_directory}}/logs/server.log. 
Redirecting output to {{#var:app_server_domain1_directory}}/logs/server.log 
Domain {{#var:app_server_default_domain}} started. 
Domain [{{#var:app_server_default_domain}}] is running [Sun Java System Application Server 9.1_01 (build local)] with its configuration and logs at: [{{#var:app_server_root}}/domains]. 
Admin Console is available at <nowiki>[https://localhost:4848]</nowiki>. 
Use the same port [4848] for "asadmin" commands. 
User web applications are available at these URLs: 
<nowiki>[http://localhost:80 https://localhost:443 ]</nowiki>. 
Following web-contexts are available: 
[/web1 /__wstx-services ]. 
Standard JMX Clients (like JConsole) can connect to JMXServiceURL: 
[service:jmx:rmi:///jndi/rmi://commsuite.eclipsecapital.com.hk:8686/jmxrmi] for domain management purposes. 
Domain listens on at least following ports for connections: 
[80 443 4848 3700 3820 3920 8686 ]. 
Domain supports application server clusters and other standalone instances. 
</blockquote>

===== Create and start the Node Agent =====

Create a new node-agent-config:

<blockquote style="padding: 1em; margin: 0 0 1.4em 1em; width: auto; background: #f9f9f9; border: 1px dashed #2f6fab; color: black; padding: 1em; line-height: 1.3em;">
{{#var:app_server_root}}/bin/asadmin create-node-agent-config --user={{#var:app_server_domain1_admin_user}} --passwordfile={{#var:app_server_root}}/passwordfile.txt {{#var:hostname}} 
Command create-node-agent-config executed successfully.
</blockquote>

Create the node-agent:

<blockquote style="padding: 1em; margin: 0 0 1.4em 1em; width: auto; background: #f9f9f9; border: 1px dashed #2f6fab; color: black; padding: 1em; line-height: 1.3em;">
{{#var:app_server_root}}/bin/asadmin create-node-agent --savemasterpassword=true --user={{#var:app_server_domain1_admin_user}} --passwordfile={{#var:app_server_root}}/passwordfile.txt {{#var:hostname}} 
Please enter the master password [Enter to accept the default]:> '''{{#var:app_server_master_password}}''' 
Command create-node-agent executed successfully. 
</blockquote>

Start the new node agent:

<blockquote style="padding: 1em; margin: 0 0 1.4em 1em; width: auto; background: #f9f9f9; border: 1px dashed #2f6fab; color: black; padding: 1em; line-height: 1.3em;">
{{#var:app_server_root}}/bin/asadmin start-node-agent --user={{#var:app_server_domain1_admin_user}} --passwordfile={{#var:app_server_root}}/passwordfile.txt {{#var:hostname}} 
Please enter the master password [Enter to accept the default]:> '''{{#var:app_server_master_password}}''' 
Redirecting output to {{#var:app_server_root}}/nodeagents/commsuite.eclipsecapital.com.hk/agent/logs/server.log 
Redirecting application output to {{#var:app_server_root}}/nodeagents/commsuite.eclipsecapital.com.hk/agent/logs/server.log 
Command start-node-agent executed successfully. 
</blockquote>

==== Test App Server ====
You should now be able to connect to the App server using the following URI's:

<blockquote class="snixblockquote">
{{#var:app_server_uri}} 
(you should get a "Your Application Server is now running" web page) 
</blockquote>

<blockquote class="snixblockquote">
Admin server: 
{{#var:app_server_admin_uri}} 
(try logging in as the admin user) 
</blockquote>

=== Access Manager 7.1 ===

Unzip the Identity Suite archive and launch the installer:

<blockquote class="snixblockquote">
unzip java_es-5u1-ga-linux-x86.zip 
cd java_es-5u1-ga-linux-x86/Linux_x86 
./installer {{#var:nodisplay}} 
</blockquote>

Plow through the "welcome" and license agreement pages to get to the component selection screen.

You only need to select the "Access Manager 7.1" and the "Core Services", "Administration Console", "Common Domain Services" and the "SDK" (they should be selected automagically when you select the Access Manager checkbox. The Directory Preparation Tool 6.4 and Directory Server Enterprise Edition 6.2 will also be automagically selected. Uncheck the Directory Server 6.2 and the Directory Perparation Tool 6.4 should automagically uncheck as well. Leave the "Install multilingual.." checkbox check as well.

When the installer barks at you... Select "A compatible web container previously installed on this system"

Directory Preparation Tool: '''/opt/sun/comms/dssetup''' 
Directory Server: '''/opt/sun''' 
Access Manager: '''/opt/sun'''

After the installer verifies the system requirements... Choose "Configure Now":

Set the Common Server Settings:

Hostname: '''{{#var:hostname}}''' 
DNS domain name: '''{{#var:domain}}''' 
IP Address: '''{{#var:ipaddress}}''' 
Administrator User ID: '''{{#var:access_manager_administration_user}}''' 
Administrator Password: '''{{#var:access_manager_administration_pass}}''' 
System user:'''root''' 
System group:'''root''' 

Directory Server: (not used, but needs to be valid)

Instance Directory: '''/var/opt/sun/directory/dsins2/'''
Directory Instance Port: '''390''' 
Directory Instance SSL Port: '''637''' 
Directory Manager DN:'''cn=Directory Manager''' 
System User: '''root''' 
System Group: '''root''' 
Directory Manager Password: '''{{#var:access_manager_admin_pass}}''' 
Suffix: '''dc=example,dc=com''' 

Specify the web container for the access manager services - make sure your '''Cookie Domain''' is correct - if it's not, you will not be able to login later. The installer does not parse 3 part TLD's correctly and will offer the wrong data as default. For example, "myhost.example.co.uk" will be offered as "co.uk" for the cookie domain:

Choose "Deploy new console" for the Access Manager Console:

Setup the directory server information:

Directory Server Host: '''{{#var:directory_server_host}}''' 
Directory Server Port: '''{{#var:directory_server_port}}''' 
Root Suffix: '''{{#var:ldap_root_suffix}}''' 
Manager DN: '''{{#var:directory_manager_dn}}''' 
Manager Pass: '''{{#var:directory_manager_dn_pass}}''' 

Since this is a brand new directory service, there is no user data yet:

All done with configuration. Hit '''Install'''

After the installation is over.. click next and you are returned to the shell where you're prompted with:

<blockquote class="snixblockquote">
In order to notify you of potential updates, we need to confirm an internet connection. Do you want to proceed [Y/N] :
</blockquote>

Answer "'''N'''" and you're done.

=== Enable Directory Service Control Centre (DSCC) ===

Create a new DSCC registry:

<blockquote class="snixblockquote">
{{#var:directory_server_root}}/dscc6/bin/dsccsetup ads-create 
Choose password for Directory Service Manager: '''{{#var:dscc_password}}''' 
Confirm password for Directory Service Manager: '''{{#var:dscc_password}}''' 
Creating DSCC registry... 
DSCC Registry has been created successfully 
</blockquote>

Edit the ''{{#var:app_server_domain1_directory}}/config/server.policy'' file to add the following required DSCC permissions:
<blockquote class="snixblockquote">
// Permissions for Directory Service Control Center 
grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/dscc/-" 
{ 
    permission java.security.AllPermission; 
}; 
</blockquote>

Now we need to deploy the ''{{#var:directory_server_root}}/var/dscc6/dscc.war'' file included with the directory server using the Application Server administration web pages. Access the Application Server administration console at

<blockquote class="snixblockquote">
https://{{#var:hostname}}:4848/
</blockquote>

Log in by using the admin username and adminpass password you defined when the Application Server was installed. To deploy application:

* Select Applications then Web Applications from the left-hand menu in the Administration Console.
* Select the Deploy option from the Web Applications menu.
* Select Local packaged file or directory that is accessible from the Application Server.
* Type the full path of the DSCC war file: ''{{#var:directory_server_root}}/var/dscc6/dscc.war'' or browse to it.
* Click the OK button at the bottom of the page.
* Log out of the Administration Console once the DSCC deployment has completed.

==== Restart Application Server ====
''(this appears to be optional)'':

{{Sun_Java_Communications_Suite_6:RestartApplicationServer}}

==== Start the DSCC registery ====

''(it should already be running)''

<blockquote class="snixblockquote">
{{#var:directory_server_root}}/ds6/bin/dsadm start {{#var:directory_server_root}}/var/dscc6/dcc/ads
</blockquote>

==== Register the Directory Server instance in the DSCC ====

* Login to the DSCC console
http://{{#var:hostname}}/dscc
* Select the Directory Servers tab.
* Select "Register Existing Directory Server" action from the More Server Actions drop-down menu.
* Type or select the following values:
** Host: '''{{#var:hostname}}'''
** Instance Path: {{#var:directory_server_data}}/{{#var:directory_server_instance_name}}
** DSCC Agent Port: 11162
** Description: '''Put something descriptive here'''
* Select the Next button to continue.
* In the Provide Authentication Information for the Host step, type the following values:
** User ID: '''root'''
** Password: '''root-password'''
''Note: Root access is required for the DSCC to be able to modify the directory service config files.''
* Select the Next button to continue.
* In the Review Server Certificate step, select the Next button.
* In the Provide Authentication Information step, type the following values:
** Administration DN: '''{{#var:directory_manager_dn}}'''
** Password: '''{{#var:directory_manager_dn_pass}}'''
* Select the Next button to continue.
* Click the Finish button to complete the process then close the window once the registration has completed.

You should now see the server commsuite.eclipsecapital.com.hk:389 listed in the Directory Servers listing.

Log out of the DSCC interface.

Sun Java Communications Suite

Nick — Wed, 01 Sep 2010 03:11:22 GMT

←Older revision		Revision as of 03:11, 1 September 2010
Line 4:		Line 4:

	[[Sun Java Communications Suite 6]] on a single node - Fedora 9 64-bit		[[Sun Java Communications Suite 6]] on a single node - Fedora 9 64-bit
		+
		+	[[Sun Java Calendar Server 7]] on Fedora 13 64-bit

Snix.hk - Recent changes [en]

Base Software Installation

Sun Java Calendar Server 7

Sun Java Communications Suite