Author: Maurice Ruckman

Posted on

XML files for Teamsite and WebMethods

From: Bojja, Sridhar (HAL Contractor)
Sent: Monday, March 19, 2012 3:11 PM
To: Ruckman, Maurice (HAL); De Vera, Marlon (HAL)
Cc: Augustine, Anila (HAL)
Subject: RE: Xml files

Talked to Marlon and Wayne and found out that they do use teamsite files that the web uses but they read it from a different location (for SBN docs we have 2. halexstreamtest and halexstreampd1)
We have redundant data one used by web and the other used by the DOX

For now we should be ok since we are going to have a new task to copy files from

\itnaswbiwebdevhalwebsite to \itnaswbihaldatawebdevhalwebsite

But when it comes time for decommissioning \itnaswbiwebdevhalwebsite and \itnaswbiwebdevcms we have to make sure that whatever process copies files to halexstreamtest and halexstreampd1 uses source as \itnaswbihaldatawebdevhalwebsite instead of \itnaswbiwebdevhalwebsite and likewise in other environments.

Also, the ftp process that sends files to fronted uses \itnaswbiwebdevhalwebsitecmsdocs

Posted on

Encrypting passwords for JBoss configuration

-----Original Message-----
From: Jeff Lindesmith [mailto:jlindesm@redhat.com]
Sent: Monday, March 19, 2012 2:47 PM
To: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Thompson, Sonya (HAL); Bojja, Sridhar (HAL Contractor); Phatak, Sheetal (HAL)
Cc: Guillaume Radde
Subject: Fwd: Database credentials and JDBC settings for Staging, Prod and Webres

Hi All,

These are the instructions I sent to Mike for encrypting the passwords.

You can look at the /deploy/hal-ds.xml file and the /conf/login-config.xml file to see how the datasource credentials are configured.
Make sure you do an "svn update" on your local vms first so that you have the latest changes to these files.

Thanks,
Jeff

----- Forwarded Message -----
From: "Jeff Lindesmith" <jlindesm@redhat.com>
To: "Mike Schumacher (HAL)" <mschumacher@hollandamerica.com>
Sent: Thursday, March 15, 2012 8:34:50 AM
Subject: Fwd: Database credentials and JDBC settings for Staging, Prod and Webres

Hi Mike,

Got this response from Dave.

Sounds like these are passwords that do not work anymore.
We will of course need passwords that do work.

I was thinking as well about how the passwords can be communicated to me for JBoss datasource configuration.
All I really need is the encrypted password that JBoss can decrypt.

You or someone else on the team can perform the following steps to generate these encrypted passwords.

1. Login to one of the JBoss infrastructure VMs, say haldevjbs01 for example.
2. Change to the main JBoss app server directory: cd /var/lib/jbossas 3. Execute the following java command (testpassword represents the actual password you want to encrypt).

java -cp client/jboss-logging-spi.jar:lib/jbosssx.jar org.jboss.resource.security.SecureIdentityLoginModule testpassword

4. The resulting encrypted password will be displayed like the following.

Encoded password: 638fb8430bc67ad6c3bc376bef610c0a

This encrypted value is all I need. So, you could send me a list of usernames and corresponding encrypted passwords.

Thanks,
Jeff

----- Forwarded Message -----
From: "David Risley (HAL)" <DRisley@HollandAmerica.com>
To: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>
Cc: "Jeff Lindesmith" <jlindesm@redhat.com>
Sent: Wednesday, March 14, 2012 1:43:27 PM
Subject: RE: Database credentials and JDBC settings for Staging, Prod and Webres

These were the original passwords that we set.  They should no longer work but you are welcome to try them:

web_owner/ befe2010
halw_dwh/ halw_dwh
siebel_ro/siebel_ro
hal_web/                 #never heard of this one.

DaveR

"Peace" - is the message really so hard to understand?

-----Original Message-----
From: Augustine, Anila (HAL)
Sent: Monday, March 12, 2012 3:03 PM
To: Risley, David (HAL)
Cc: Jeff Lindesmith; Schumacher, Mike (HAL)
Subject: RE: Database credentials and JDBC settings for Staging, Prod and Webres
Importance: High

Hi Dave,

Could you please help with the request below?

Thanks
Anila

________________________________________
From: Lindesmith, Jeff (HAL)
Sent: Thursday, March 08, 2012 12:51 PM
To: Risley, David (HAL)
Cc: guillaume.radde@redhat.com; rgullett@redhat.com; Schumacher, Mike (HAL)
Subject: Database credentials and JDBC settings for Staging, Prod and Webres

Hi Dave,

Basically, what we need are the username and passwords used by Websphere to connect to databases and the JDBC connection urls.

For example, on dev we have the following connection urls with corresponding credentials.

connection url = jdbc:oracle:thin:@//haltstdbs02:37200/devweb

username = web_owner
password = web_owner

connection url = jdbc:oracle:thin:@haltstdb01.hq.halw.com:17101:devdwh1

username = halw_dwh
password = halw_dwh

connection url = jdbc:oracle:thin:@//haltstcrm01:2900/tstcrm1

username = siebel_ro
password = siebel_ro

connection url = jdbc:oracle:thin:@10.194.100.103:1521:tsgp

username = hal_web
password = hal_web

connection url = jdbc:oracle:thin:@haltstdbs05.hq.halw.com:17401:tstdwh1

username = halw_dwh
password = halw_dwh

We need the equivalent settings for these connections for the Staging, Production and Webres environments.

Thanks,
Jeff Lindesmith
Senior Consultant
Red Hat Consulting

 

-----Original Message-----
From: Jeff Lindesmith [mailto:jlindesm@redhat.com]
Sent: Monday, March 19, 2012 2:47 PM
To: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Thompson, Sonya (HAL); Bojja, Sridhar (HAL Contractor); Phatak, Sheetal (HAL)
Cc: Guillaume Radde
Subject: Fwd: Database credentials and JDBC settings for Staging, Prod and Webres

Hi All,

These are the instructions I sent to Mike for encrypting the passwords.

You can look at the /deploy/hal-ds.xml file and the /conf/login-config.xml file to see how the datasource credentials are configured.

Make sure you do an "svn update" on your local vms first so that you have the latest changes to these files.

Thanks,

Jeff

----- Forwarded Message -----

From: "Jeff Lindesmith" <jlindesm@redhat.com>

To: "Mike Schumacher (HAL)" <mschumacher@hollandamerica.com>

Sent: Thursday, March 15, 2012 8:34:50 AM

Subject: Fwd: Database credentials and JDBC settings for Staging, Prod and Webres

Hi Mike,

Got this response from Dave.

Sounds like these are passwords that do not work anymore.

We will of course need passwords that do work.

I was thinking as well about how the passwords can be communicated to me for JBoss datasource configuration.

All I really need is the encrypted password that JBoss can decrypt.

You or someone else on the team can perform the following steps to generate these encrypted passwords.

1. Login to one of the JBoss infrastructure VMs, say haldevjbs01 for example.

2. Change to the main JBoss app server directory: cd /var/lib/jbossas 3. Execute the following java command (testpassword represents the actual password you want to encrypt).

java -cp client/jboss-logging-spi.jar:lib/jbosssx.jar org.jboss.resource.security.SecureIdentityLoginModule testpassword

4. The resulting encrypted password will be displayed like the following.

Encoded password: 638fb8430bc67ad6c3bc376bef610c0a

This encrypted value is all I need. So, you could send me a list of usernames and corresponding encrypted passwords.

Thanks,

Jeff

----- Forwarded Message -----

From: "David Risley (HAL)" <DRisley@HollandAmerica.com>

To: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>

Cc: "Jeff Lindesmith" <jlindesm@redhat.com>

Sent: Wednesday, March 14, 2012 1:43:27 PM

Subject: RE: Database credentials and JDBC settings for Staging, Prod and Webres

These were the original passwords that we set. They should no longer work but you are welcome to try them:

web_owner/ befe2010

halw_dwh/ halw_dwh

siebel_ro/siebel_ro

hal_web/ #never heard of this one.

DaveR

"Peace" - is the message really so hard to understand?

-----Original Message-----

From: Augustine, Anila (HAL)

Sent: Monday, March 12, 2012 3:03 PM

To: Risley, David (HAL)

Cc: Jeff Lindesmith; Schumacher, Mike (HAL)

Subject: RE: Database credentials and JDBC settings for Staging, Prod and Webres

Importance: High

Hi Dave,

Could you please help with the request below?

Thanks

Anila

________________________________________

From: Lindesmith, Jeff (HAL)

Sent: Thursday, March 08, 2012 12:51 PM

To: Risley, David (HAL)

Cc: guillaume.radde@redhat.com; rgullett@redhat.com; Schumacher, Mike (HAL)

Subject: Database credentials and JDBC settings for Staging, Prod and Webres

Hi Dave,

Basically, what we need are the username and passwords used by Websphere to connect to databases and the JDBC connection urls.

For example, on dev we have the following connection urls with corresponding credentials.

connection url = jdbc:oracle:thin:@//haltstdbs02:37200/devweb

username = web_owner

password = web_owner

connection url = jdbc:oracle:thin:@haltstdb01.hq.halw.com:17101:devdwh1

username = halw_dwh

password = halw_dwh

connection url = jdbc:oracle:thin:@//haltstcrm01:2900/tstcrm1

username = siebel_ro

password = siebel_ro

connection url = jdbc:oracle:thin:@10.194.100.103:1521:tsgp

username = hal_web

password = hal_web

connection url = jdbc:oracle:thin:@haltstdbs05.hq.halw.com:17401:tstdwh1

username = halw_dwh

password = halw_dwh

We need the equivalent settings for these connections for the Staging, Production and Webres environments.

Thanks,

Jeff Lindesmith

Senior Consultant

Red Hat Consulting

Posted on

Creating a RC (Release Candidate)

From command line:

1. http://halsvn01/websvn/ copy the link for SVN for the branch being tagged, remove trailing slash from source of copy on next step
2. svn copy http://halsvn01/svn/hal/branches/RC/12.11-RC http://halsvn01/svn/hal/tags/12.11-RC1 -m "Tagging current RC branch to 12.11-RC1"

Creating a Release Candidate from Eclipse:

1. Open SVN Repository Explorer in Eclipse
2. Expand to current RC branch (ex. 12.11-RC), and right-click
3. Choose branch/tags option
4. Choose "Copy to URL", "Select" and choose "tags" directory
5. http://halsvn01/svn/hal/tags/12.11-RC1 (YY.WK-RC1)
6. Next, Next
7. Use a comment, example: "Tagging current RC branch to 12.11-RC1"
8. Finish

Update Hudson Job
1. Login to Hudson
2. hal-tst
3. Configure
4. Refresh Page
5. Change Project description to reflect release candidate
6. Change Repository URL
7. Click save and answer prompts, if necessary
8. Go to Dashboard and hit refresh
9. Hit refresh

Posted on

Errors during VM update, JBoss no longer starts

The following two files were missing:

  • /usr/lib/jvm/java-1.6.0/jre/lib/security/US_export_policy.jar
  • /usr/lib/jvm/java-1.6.0/jre/lib/security/local_policy.jar

Example error log snippet:

15 Mar 2012 21:19:27,768 ERROR AbstractKernelController : incrementState : 959 - Error installing to Start: name=WebServer state=Create
java.lang.NoClassDefFoundError: Could not initialize class javax.crypto.SunJCE_b
at javax.crypto.Cipher.getInstance(DashoA13*..)
at com.sun.net.ssl.internal.ssl.JsseJce.getCipher(JsseJce.java:180)

Posted on

Using Maven

-----Original Message-----
From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Thursday, March 15, 2012 10:40 AM
To: Ruckman, Maurice (HAL)
Cc: Fillman, Eric (HAL); Phatak, Sheetal (HAL); Thompson, Sonya (HAL); Bojja, Sridhar (HAL Contractor)
Subject: Re: FYI JBOSS - Almost as good as an exploded WAR

Exploded deployment and faster modify/test cycle will come as a side effect of the maven migration, currently in progress in the "goodbye-ant" feature branch. Anybody can try it by doing:

$ svn co http://halsvn01/svn/hal/branches/features/goodbye-ant hal $ cd hal $ mvn install

Guillaume

Posted on

How to Install Eclipse and Create Projects

Pre-steps

Setup HAL Formatting
Turn off Project, Build Automatically

Start Project Setup via Repository

Open a Perspective "SVN Repository Explorer"

Right-click blank window, New, Respository Location
http://halsvn01/svn/hal

Go into preferences, search for Workspace and have it "Prompt for workspace on startup"
NOTE: When machines are currently imaged, the wrong default workspace is set

Right-click SVN Repositories
branchesfeaturesjboss-migration (current release candidate or the like)

and click "Checkout"
Use the wizard, "Check out as a project configured using the New Project Wizard", "Check out HEAD revision", "Allow unversioned obstructions" (defaults)
Click "Finish"

Wizards: Java Project, Next
Project Name: HAL, "Use default location" /home/jboss1/workspace/HAL, "Create separate folders for sources and class files"
Use an execution environment JRE: JavaSE-1.6
Click "Finish"

Click "OK" for Java Perspective
Click "OK" for confirm overwrite process

Right Click the project branch HAL, Build Path, Configure Build Path...
Source, Remove "HAL/src"
"Add Folder", Click "OK"
Check "HAL" and Click "OK"

Included: (All), Edit
"Add Multiple" "com" (com/)
Click "OK"
Click "Finish"

Click "OK"

Setup JBoss Server for Runtime and Debugging

File, New, Other, Server

Server, Next "jBoss AS 5.1"

server's host name "haldevjbs04.hq.halw.com"

Next

Name: JBoss Runtime

Home Directory: /home/jboss1/programs/jboss-eap-5.1/jboss-as

JRE: java-1.6.0-sun-1.6.0.31.x86_64

Directory: sever
and then highlight: "haldev-vm-template"

Then click "Finish"

Configure JBoss Server for Performance

Windows, Show View, Servers

Now you have a tab down in the lower window section

Double-click the "JBoss 5.1 Runtime Server [Stopped]" icon to open setup

"Open Launch Configuration" link

VM arguments: (need updated)

-Xmx768m -> -Xmx1024m

Scroll to the bottom, and add (preceed with a space)
-Djboss.jvmroute=haldevjbs04.hq.halw.com

Then click "OK" to finish the server configuration.

Complete Project Setup by Adding Jar Files

Right-click your project, in the Package Explorer

Configure build path, "Add Library" "Server Runtime", Next, "JBoss 5.1 Runtime"
Finish, and OK

Add Jars "Java Build Path", "Libraries", "Add JARs"
choose HAL project put *jar in the filter
expand all branches, and then select all of the jar files
Click "OK" once you have deselected all of the folder nodes

Post-steps

Turn on Project, Build Automatically
Install PMD

Posted on

How to revert code to an earlier version

-----Original Message-----
From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Friday, March 16, 2012 12:36 PM
To: Ruckman, Maurice (HAL)
Cc: Doan, Thomas (HAL Contractor); Fillman, Eric (HAL); Augustine, Anila (HAL); Thompson, Sonya (HAL); Phatak, Sheetal (HAL); Bojja, Sridhar (HAL Contractor); jlindesm@redhat.com; HAL DistList: IS UNIX; Tripp, Donald (HAL)
Subject: Re: Yum update haldevjbs06

Not sure. Try this from the /home/jboss1/programs/jboss-eap-5.1/jbossas/server/haldev-vmtemplate folder:

$ svn log

--->Look at the revision number you want to rollback to

$ svn update -r MyRevNumbder

Guillaume

Posted on

Creating a new branch

To create a new branch, in Eclipse in the svn repository explorer, right click on the folder 12.11-RC and select create branch. The new location should be something like http://halsvn01/svn/hal/branches/features/fix-security-settings

Or from the command line:

$ svn copy http://halsvn01/svn/hal/branches/RC/12.11-RC http://halsvn01/svn/hal/branches/features/simplified-welcome-page -m "Creating feature branch simplified-welcome-page"