Download and Install CollabNet Subversion in Solaris

CollabNet Subversion Download Link: http://www.collab.net/downloads/subversion/solaris.html 1. Platform and configuration

Product: CollabNet Subversion client
Platforms: Solaris 10 SPARC

Prerequisite: You must be a superuser (root) to install and uninstall CollabNet Subversion. 2. Import/Update CollabNet certificate CollabNet Subversion Solaris packages are signed. As a one-time task, import the CollabNet certificate using the command:     sudo pkgadm addcert -ty certificate.pem The CollabNet certificate is available for download at: http://www.collab.net/nonav/downloads/subversion/certificate/certificate.pem NOTE: the certificate has changed between 1.5.0 and 1.5.1 release.  The certificate used for 1.5.0 had a short expiration date so we have created a new certificate.  If you have previously installed the 1.5.0 certificate, you must remove it before installing the new one:     sudo pkgadm removecert “Alexander Thomas(AT)” Once it is removed you can install the new certificate. 3. First installation The command to install the CollabNet Subversion client, if a previous version has not already been installed, is:     sudo pkgadd -d /path/to/client-sparc-local 4. Updating an existing installation The proper way to update a Solaris package is to remove the current version and then install the new version.  If you have the CollabNet Subversion server installed, you will need to remove it first.  Again, refer to the readme for that package before proceeding.     sudo pkgrm CSVNclnt     sudo pkgadd -d /path/to/client-sparc-local 5. Post-installation instructions A. CollabNet Subversion installs into /opt/CollabNet_Subversion, which is    probably not on the executable search path for your system. Add the directory    /opt/CollabNet_Subversion/bin to your $PATH environment variable. In order to    make this change affect all users of your system and persists across reboots,    add the following line to /etc/profile:     PATH=/opt/CollabNet_Subversion/bin:$PATH B. CollabNet Subversion provides man pages and localizations for several    languages. To take advantage of these features, update your MANPATH and/or    LOCPATH environment variables to include the CollabNet Subversion directories.     For example:     export MANPATH=/opt/CollabNet_Subversion/share/man:$MANPATH     export LOCPATH=/opt/CollabNet_Subversion/share/locale:$LOCPATH 6. Support for CollabNet Subversion Find out about CollabNet Technical Support at http://www.collab.net/services/subversion/    Information about CollabNet Training, Consulting, and Migration services is at http://www.collab.net/services/subversion/training.html    Join openCollabNet for community support: http://open.collab.net 7. About Subversion and CollabNet CollabNet launched the Subversion project in 2000 in response to the demand for an open standard for Web-based software configuration management that could support distributed development. CollabNet continues to be strongly involved with the Subversion project and offers CollabNet Subversion Support, Training, and Consulting services.    CollabNet also provides the most widely used collaborative development environment in the world. More than 1,400,000 developers and IT projects managers collaborate online through CollabNet. The company is transforming the way software is developed by enabling organizations to leverage global development talents to deliver better products and innovate faster.    Visit CollabNet at http://www.collab.net for more information

Thanks to:  http://www.scmgalaxy.com


Suggestions are always welcome..!  Without signing also you can send your comments.

Struts Download

http://struts.apache.org/download.cgi


Suggestions are always welcome...! Without signing also you can send your comments.

JBOSS - Integration With WebSphere MQ

JBOSS - Integration With WebSphere MQ

 

WebSphere MQ Series Integration with JBoss Application Server v4.x and v3.2.x

This wiki provides various resources to integrate WebSphere MQ Series 5.x in JBoss Application Server.

• Using WebSphere MQ Series with JBossAS Part I - Common use case, JBossAS talking to WSMQ with XA support
• Using WebSphere MQ Series with JBossAS Part II - WSMQ used in place of JBossMQ
• Using WebSphere MQ Series with JBossAS Part III - Integration using an external context
• Using WebSphere MQ Series with JBossAS Part IV - Integration using the IBM WebSphere JMS Resource Adapter  (RECOMMENDED WAY!!) 
  
  
  
  

 Suggestions are always welcome...! Without signing also you can send your comments.

Configuring SSL for JBoss Application Server

To configure SSL on JBoss® Application Server, you need an SSL credential for authentication. You can use the Java keytool to create a credential or request and import a credential from a certificate authority (CA). You must then enable SSL on JBoss.

You can run keytool by using a single command that includes all of the information needed to create the keystore.

In this procedure:

• [appserver root] is the home directory of the application server running LiveCycle ES2.
• [type] is a folder name that varies, depending on the type of install you performed. It may be lc_turnkey, lc_mysql, lc_oracle, lc_oracle_cl,lc_sqlserver, or lc_sqlserver_cl.

Create an SSL credential

1. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to create the credential and keystore:
   keytool -genkey -dname "CN=Host Name, OU=Group Name, O=Company Name,L=City Name, S=State, C=Country Code" -alias "LC Cert" -keyalg RSA -keypass key_password -keystore keystorename.keystore
   Note: Replace [JAVA_HOME] with the directory where the JDK is installed, and replace the text in italic with values that correspond with your environment. Host Name is the fully qualified domain name of the application server.
2. Enter the keystore_password when prompted for a password. The password for the keystore and the key must be identical.
   Note: The keystore_password entered at this step may be the same password (key_password) that you entered in step 1, or it may be different.
3. Copy the keystorename.keystore to the [appserver root]/server/[type]/conf directory by typing one of the following commands:
   • (Windows) copy keystorename.keystore [appserver root]\server\[type]\conf
   • (Linux) cp keystorename.keystore [appserver root]/server/[type]/conf
4. Export the certificate file by typing the following command:
   keytool -export -alias "LC Cert" -file LC_cert.cer -keystore[appserver root]\server\[type]\conf\keystorename.keystore
5. Enter the keystore_password when prompted for a password.
6. Copy the LC_cert.cer file to the [appserver root] conf directory by typing the following command:
   • (Windows) copy LC_cert.cer [appserver root]\server\[type]\conf
   • (Linux) cp LC_cert.cer [appserver root]/server/[type]/conf
7. View the contents of the certificate by typing the following command:
   keytool -printcert -v -file [appserver root]\server\[type]\conf\LC_cert.cer
8. To provide write access to the cacerts file in [JAVA_HOME]\jre\lib\security, if required, perform the following task:
   • (Windows) Right-click the cacerts file and select Properties, and then deselect the Read-only attribute.
   • (Linux) Type chmod 777 cacerts
9. Import the certificate by typing the following command:
   keytool -import -alias "LC Cert" -file LC_cert.cer -keystore JAVA_HOME\jre\lib\security\cacerts
10. Type changeit as the password. This password is the default password for a Java installation and may have been changed by the system administrator.
11. When prompted for Trust this certificate? [no]:, type yes. The confirmation "Certificate was added to keystore" is displayed.
12. If you are connecting over SSL from LiveCycle Workbench ES2, install the certificate on the Workbench ES2 server.
13. In a text editor, open the server.xml file from the directory:
    • (JBoss Application Server 4.0.3) [appserver root]/server/[type]/deploy/jbossweb-tomcat55.sar
    • (JBoss Application Server 4.2) [appserver root]/server/[type]/deploy/jboss-web.deployer
14. In the server.xml file, uncomment the following section:
    <!-- SSL/TLS Connector configuration using the admin devl guide keystore <Connector port="8443" address="${jboss.bind.address}" maxThreads="100" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" scheme="https" secure="true" clientAuth="false" keystoreFile="${jboss.server.home.dir}/conf/keystoreFile.keystore" keystorePass="keystorePass" sslProtocol = "TLS" />
    -->
15. Change the value for the keystoreFile attribute and the keystorePass attribute to the keystore password that you specified when you created the keystore (shown in the example above).
16. Save the server.xml file.
17. Restart the application server:

• For turnkey installations:
  • From the Windows Control Panel, click Administrative Tools, and then click Services.
  • Select JBoss for Adobe LiveCycle ES2.
  • Select Action > Stop.
  • Wait for the status of the service to appear as stopped.
  • Select Action > Start.
• For Adobe preconfigured or manually configured JBoss installations:
  • From a command prompt, navigate to [appserver root]/bin.
  • Stop the server by entering the following command:
    • (Windows) shutdown.bat -S
    • (Linux) ./shutdown.sh -S
  • Wait until the JBoss process has fully shut down (when the JBoss process returns control to the terminal it was started in).
  • Start the server by entering the following command:
    • (Windows) run.bat -c all
    • (Linux) ./run.sh -c all

1. To access LiveCycle Administration Console using SSL, type https://[host name]:[port]/adminui in a web browser:
   The default SSL port for JBoss is 8443. From here on, specify this port when accessing LiveCycle ES2.

Request a credential from a CA

1. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to create the keystore and the key:
   keytool -genkey -dname "CN=Host Name, OU=Group Name, O=Company Name, L=City Name, S=State, C=Country Code" -alias "LC Cert" -keyalg RSA -keypass key_password -keystore keystorename.keystore
   Note: Replace [JAVA_HOME] with the directory where the JDK is installed, and replace the text in italic with values that correspond with your environment.
2. Type the following command to generate a certificate request to send to the certificate authority:
   keytool -certreq -alias "LC Cert" -keystore keystorename.keystore -file LCcertRequest.csr
3. When your request for a certificate file is fulfilled, complete the next procedure.

Use a credential obtained from a CA to enable SSL

1. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to import the root certificate of the CA with which the CSR has been signed:
   keytool -import -trustcacerts -file rootcert.pem -keystore keystorename.keystore -alias root
   If the root certificate is not in the browser, also import it there.
   Note: Replace [JAVA_HOME] with the directory where the JDK is installed, and replace the text in italic with values that correspond with your environment.
2. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to import the credential into the keystore:
   keytool -import -trustcacerts -file CACertificateName.crt -keystore keystorename.keystore
   Note: Replace [JAVA_HOME] with the directory where the JDK is installed, and replace the text in italic with values that correspond with your environment.
   Note: The imported CA signed certificate will replace a self-signed public certificate if it exists.
3. 1. Set Basic Authentication to Supported, set Client Certificate Authentication to Supported, and then click OK.
   2. Navigate to CSIv2 Outbound Authentication and then click Security > Secure Administration, Applications and Infrastructure and, under Authentication, click RMI/IIOP Security > CSIv2 Outbound Authentication.
   3. Set Basic Authentication to Supported, set Client Certificate Authentication to Supported, and then click OK.
   4. Navigate to CSIv2 Inbound Transport and then click Security > Secure Administration, Applications and Infrastructure and, under Authentication, click RMI/IIOP Security > CSIv2 Inbound Transport.
   5. Set Transport to SSL-Supported and SSL Settings to localhost/AdsSSL, and then click OK.
   6. Navigate to CSIv2 Outbound Transport and then click Security > Secure Administration, Applications and Infrastructure and, under Authentication, click RMI/IIOP Security > CSIv2 Outbound Transport.
   
   
   
   
   
   Thanks to: http://help.adobe.com

Suggestions are always welcome...! Without signing also you can send your comments.