Setup POLAR Hotspot and Rules for Testing

Refer: To set up a HOTSPOT Key.docx

From: randerson@princesscruises.com [mailto:randerson@princesscruises.com]
Sent: Thursday, February 09, 2012 3:20 PM
To: Fernan, Diana (HAL Contractor)
Cc: Konar, Tara (PCL); Augustine, Anila (HAL); Mounagurusamy, Jayakumar (HAL); Ruckman, Maurice (HAL); Harrington, Scott (HAL Contractor)
Subject: Hot Spot set up for POLAR and Test Rules

Diana,

Sorry this took me a little longer than expected.

Below is a word document for setting up POLAR for Hotspot use.

Also, there are a few rules that need to be followed with regards to creating test air bookings.

1. Use bookings in POLAR which you know you created or at minimum are bookings you know where not loaded into the test region from Production.

2. When possible, use dates that are far out (6 months and beyond). If for some reason you must create records where the itin leaves within 7 days, you should advise Kristen or her designee so that they can immediately cancel the PNR. This should only be done on very rare cases for specific testing scenarios.

3. Use realistic names only i.e. Frank Johnson, Kelly Smith etc.

DO NOT USE

  • Cartoon Names
  • Celebrity Names
  • 'Test' names ie. TestUser1
  • or any other unrealistic names

4. Do not use the same name to build several Sabre PNRs
In other words don't use Frank Johnson for every booking you create in POLAR.  If you would like to continue using a booking try cancelling any air off the booking and then changing the passengers names completely before trying to book again using that booking

These rules apply because we are testing against the Sabre Production environment. This is necessary because they (Sabre) do not support their Certification environment which makes getting real search results and creating bookings difficult. We have a hard time telling when errors are related to Sabre data issues or our system issues.

I think that is about it. Penalties have been threatened by Sabre for violations of the above, so please keep the rules in mind.

Thanks everyone, please let me know if you have any questions.

Rich

Richard Anderson
Sr. Business Analyst
Reservations Systems Development
661-2844372

Using ezAir Admin Tool

Refer: EZ Air Admin Tool Reference.doc

From: tkonar@princesscruises.com [mailto:tkonar@princesscruises.com]
Sent: Thursday, February 09, 2012 8:45 AM
To: Ruckman, Maurice (HAL)
Cc: Augustine, Anila (HAL); Fernan, Diana (HAL Contractor); Mounagurusamy, Jayakumar (HAL); Anderson, Richard (PCL); Harrington, Scott (HAL Contractor)
Subject: RE: User IDs for access to HAL eZAir test logs

Hi Maurice,
Application is not working as there is no data setup in the admin tool. I worked with Jay back in November to show him how to enter all the data. In future this admin tool will be maintained by your air department. So someone from the air department needs to be familiar with this admin tool. I am attaching a document that explains all the different features of the admin tool.

I am trying to set up the data in HAL eZair admin tool and after that you will have to bounce eZair application server (WebSphere) in order for these changes to get reflected on the eZair app. I will let you know once all the data is setup.

To add a user for the admin tool, you will have to enter user details from the admin tool and then log into the database and assign a password for that user (in AIR_ADM_USER_MST table). Please assign a password for my ID "tara" so that I can use my ID to log into the tool.

Thanks,

Tara Konar
IT Web Projects - Internet
Princess Cruises
(661) 284-4371

From: Mounagurusamy, Jayakumar (HAL)
Sent: Tuesday, February 07, 2012 2:33 PM
To: Fernan, Diana (HAL Contractor); Anderson, Richard (PCL); Ruckman, Maurice (HAL)
Cc: Augustine, Anila (HAL); McConnell, Chris (HAL Contractor); Tonks, Kristen (HAL); Schumacher, Mike (HAL); Harrington, Scott (HAL Contractor); Bueing, Teresa (HAL); Konar, Tara (PCL); Hofsetz, Therron (HAL)
Subject: RE: Fw: User IDs for access to HAL eZAir test logs

Diana,

The ezAir  admin tool should be work now. Please try  and let us know if you run into any problem.

http://haltstapp03/airadmin/login
username - jay
password - jay123

Diana and Scott were originally using this link:
https://ht.hq.halw.com/airadmin

Adding a User to ezAir

From: tkonar@princesscruises.com [mailto:tkonar@princesscruises.com]
Sent: Thursday, February 09, 2012 8:54 AM
To: Ruckman, Maurice (HAL)
Cc: Augustine, Anila (HAL); Fernan, Diana (HAL Contractor); Mounagurusamy, Jayakumar (HAL); Anderson, Richard (PCL); Harrington, Scott (HAL Contractor)
Subject: RE: User IDs for access to HAL eZAir test logs

To add a user for the admin tool, you will have to enter user details from the admin tool and then log into the database and assign a password for that user (in AIR_ADM_USER_MST table). Please assign a password for my ID "tara" so that I can use my ID to log into the tool.

Thanks,

Tara Konar
IT Web Projects - Internet
Princess Cruises
(661) 284-4371

URL Link does not work from POLAR

From: randerson@princesscruises.com [mailto:randerson@princesscruises.com]
Sent: Thursday, February 09, 2012 9:49 AM
To: Konar, Tara (PCL)
Cc: Augustine, Anila (HAL); Fernan, Diana (HAL Contractor); Mounagurusamy, Jayakumar (HAL); Ruckman, Maurice (HAL); Harrington, Scott (HAL Contractor)
Subject: RE: User IDs for access to HAL eZAir test logs

Thanks for your response Tara, you can obviously ignore my last email to you.

For everyone on the HAL side. In Diana's earlier email she mentioned not being able to use the URL from the POLAR screen. There is a configuration which must be set up within the terminal to allow for the use of 'Hotspots'. I will send out a separate email with instructions for how to set this up as well as some general rules that need to be followed while testing eZAir.

I will send this email out in a few minutes.

Thanks,

Rich

Richard Anderson
Sr. Business Analyst
Reservations Systems Development
661-2844372

VM Observations

Things to Consider

  • Developers do not have root access
    • May not be able to override some settings
    • Will not know how admin configurations work, need to rely upon Unix team
    • Should match environments, if in synch
    • Maybe we need a root machine as a sandbox for playing with jBoss configurations, otherwise we rely upon Unix team for all configuration knowledge
  • Who will support the VM's and re-imaging of them when necessary
  • xManager seems to have issues after staying open for several hours on our machines, this appears to be an xManager issue, also once the session is closed everything stops
  • Slight delay when switching screens, and copy/pasting
  • Turning on session replication
    • Session size is important to watch again!
    • Page will crash if session object is NOT serializable
  • Unable to print
  • Remotely connect to Linux VM directly (rather than through work PC)
    • Mike Schumacher said that this might be doable if (1) we use apps.halw.com to instead of vpn.halw.com and (2) he would install XManager client on the Citrix Server. He said that they would need to set up access rights for me so that I could test it.
  • Local development should explode the EAR file to avoid having to do a complete build to change a JSP
  • Quirks in Jboss dev studio that I should be able to fix myself, but haven’t yet
    • Not getting help from the IDE like code complete (where you type an object and all the methods come up)
    • If I have an issue (like missing an import, etc.), the line is not highlighted red, the import statement isn’t automatically added like it is in the Eclipse that I used to use, and I can’t tell until I do a build
    • How do we run in debug mode where we can set breakpoints?
  • Quirk with the VM
    • Cannot reboot the VM
    • Sonya Hint: Hitting XManager’s Close button (x button) kills the gnome session, which kills everything. When you are using XManager, when you are done, you should close all apps and then go to System >> Log off

Missing Files / Folders

  • C:changeManhalwebsitechip
  • C:changeManhalwebsiteHALWShxAdm
  • C:changeManhalwebsitecomhalwappletURLReader.class
  • C:changeManhalwebsiteconfigexcludeexcludeSelling.xml
  • C:changeManhalwebsiteincludes
  • C:changeManhalwebsitejs*
  • C:changeManhalwebsitesbnstylesf* (many)
  • C:changeManhalwebsitesbnstyleufhalSupplement.css
  • C:changeManhalwebsitesbnviewsf*
  • C:changeManhalwebsitestylelocalized*
  • C:changeManhalwebsitestylesf*
  • C:changeManhalwebsitestyleuf*
  • C:changeManhalwebsitestyle*
  • C:changeManhalwebsiteutilities*
  • C:changeManhalwebsiteview*
  • C:changeManhalwebsiteviewsf*
  • C:changeManhalwebsitewebbkgresource* (use?)
  • C:changeManhalwebsitewebbkg* (use?)
  • C:changeManhalwebsiteWEB-INF*

Other Items

C:changeManhalwebsite* (see below)
Error.jsp
pleasewait.modal.inc.xml
ShxAdmScreenDefinitions.jsp
ShxAdmTemplate.jsp
sitemap.xml

Forced Overnight Logic FON

Reference: Forced Overnight Logic

From: Mounagurusamy, Jayakumar (HAL)
Sent: Friday, January 20, 2012 12:58 PM
To: Thompson, Sonya (HAL); Harris, Tyrone (HAL); Ruckman, Maurice (HAL)
Subject: FW: AGEL-8QE2SW - DOT Regulations - Add booking with Forced Overnight auto applied

Sonya,

Please see the solution from PCL to deal with declining the FON package.

Jay

From: jchandran@princesscruises.com [mailto:jchandran@princesscruises.com]
Sent: Friday, January 20, 2012 11:03 AM
To: Mounagurusamy, Jayakumar (HAL)
Cc: Smith, Gabrielle (HAL); Davidson, Larry (PCL)
Subject: RE: AGEL-8QE2SW - DOT Regulations - Add booking with Forced Overnight auto applied

Jay,

Please find below the Invoice Pricing request XML and Create Booking XML. Let us know if you need any changes in the proposed XML.

The new element DeleteFOPackage may have three values "Pre", "Post" or "Both".
Pre   --> Delete the pre "FO" packages and replace them with system generated on-own packages
Post --> Delete the post "FO" packages and replace them with system generated on-own packages
Both --> Delete both the pre & post "FO" packages and replace them with system generated on-own packages

Invoice Pricing Request

<CruiseLineRequest>
<MessageHeader SegmentId="MSGHDR">
<MessageId>CCINVPR1</MessageId>
<SessionId>vSLh2QdEpPj5tylEjzh-eZ3</SessionId>
<CruiseLineCode>HAL</CruiseLineCode>
<SystemId>BH</SystemId>
<UserId>HALFE</UserId>
<AgencyId>DIRECT</AgencyId>
<UICode>7</UICode>
<VersionNum>3.0</VersionNum>
<AttemptCnt>1</AttemptCnt>
<SendDescriptionInd>Y</SendDescriptionInd>
<Advisory/>
</MessageHeader>
<InvoicePricingRequest SegmentId="INVPR1">
<SailingId>W220</SailingId>
<SailDate>03112012</SailDate>
<Ship Code="WE"/>
<Currency Code="USD"/>
<Tour/>
<Share/>
<Rate Code="RH4"/>
<Category Code="NN"/>
<Cabin Number="4012"/>
<DeleteFOPackage="Both"/ >
<Guest SeqNumber="1">
<InsuranceInd>N</InsuranceInd>
<Nationality/>
<Transportation TypeCode="A" CityCode="SEA"/>
<Package Code="B0TNOXFR" TypeCode="B"/>
<Package Code="A0TNOXFR" TypeCode="A"/>
<SpecialService TypeCode="UPG" Code="Y"/>
<Age Code="Y" Amount="40"/>
<Gender Code="m"/>
<PastGuestNumber/>
<FirstName>JOHNQ</FirstName>
<LastName>PUBLIC</LastName>
</Guest>
</InvoicePricingRequest>
</CruiseLineRequest>

Create Booking Request

<CruiseLineRequest>
<MessageHeader SegmentId="MSGHDR">
<MessageId>CCNEWBK1</MessageId>
<SessionId>vSLh2QdEpPj5tylEjzh-eZ3</SessionId>
<CruiseLineCode>HAL</CruiseLineCode>
<SystemId>BH</SystemId>
<UserId>HALFE</UserId>
<AgencyId>DIRECT</AgencyId>
<UICode>7</UICode>
<VersionNum>3.0</VersionNum>
<AttemptCnt>1</AttemptCnt>
<SendDescriptionInd>Y</SendDescriptionInd>
<Advisory/>
</MessageHeader>
<CreateReviseRequest SegmentId="BKCRV1">
<SailingId>W220</SailingId>
<SailDate>03112012</SailDate>
<Ship Code="WE"/>
<Currency Code="USD"/>
<Tour/>
<Share/>
<Rate Code="RH4"/>
<Category Code="NN"/>
<BedConfiguration Code="NP"/>
<Cabin Number="4012"/>
<DeleteFOPackage="Both"/ >
<DiningSeating Code="8" TableCode="N"/>
<Guest ActionCode="N" SeqNumber="1">
<InsuranceInd>N</InsuranceInd>
<Nationality/>
<CountryofResidence/>
<ContactPhone/>
<PastGuestInd>N</PastGuestInd>
<Transportation TypeCode="A" CityCode="SEA" DirectionCode="R"/>
<Package Code="B0TNOXFR" TypeCode="B"/>
<Package Code="A0TNOXFR" TypeCode="A"/>
<SpecialService TypeCode="UPG" Code="Y"/>
<Language/>
<Age Code="Y" Amount="40"/>
<BirthDate>01011972</BirthDate>
<Gender Code="m"/>
<PastGuestNumber/>
<Title Code="Mr"/>
<FirstName>JOHNQ</FirstName>
<MiddleName>NMN</MiddleName>
<LastName>PUBLIC</LastName>
</Guest>
<DocumentDelivery/>
<ConsumerInfo>
<LastName>PUBLIC</LastName>
<FirstName>JOHNQ</FirstName>
<Eref>mruckman@hollandamerica.com</Eref>
<Address1>300 ELLIOTT AVE W</Address1>
<Address2/>
<City>SEATTLE</City>
<StateCode>WA</StateCode>
<CountryCode>US</CountryCode>
<ZipCode>98026</ZipCode>
<ContactPhone TypeCode="H" Number="2062223333"/>
</ConsumerInfo>
</CreateReviseRequest>
</CruiseLineRequest>

Lost menu panel when loggin onto VM “Panel Already Running”

Got the following message when trying to remote onto my VM using xStart:
"I've detected a panel already running and I will now exit"

Fix was to right-click the desktop, open a terminal and run the following command:
gnome-system-monitor

This is the same as a windows process explorer. Find the "gnome-panel" processes and kill them. Close your session and restart. All should be good again.

Checkout files in svn

mkdir ~/test_workshop
cd ~/test_workshop
svn checkout http://halsvn01/svn/hal-test/trunk hal

Real production files are here:
svn checkout http://halsvn01/svn/hal/branches/features/jboss-migration/ hal

It will now prompt you for the jboss1/holland123 credentials
use your network signon /123 to now checkout the repository files

Reset defaults in SubVersion

Use the following command to remove all of the previous settings for subversion, necessary because the VM was cloned from Eric's machine, and we all inherited his settings.  Need subversion to ask for our userid / password when checking out files.

rm -rf ~/.subversion/