Posts

Posted on

Using Fiddler with an iPad

You can monitor an iPad's traffic with Fiddler 2 and a PC

Fiddler 2 Setup

1. Install Fiddler http://www.fiddler2.com/fiddler2/version.asp

2. Tools > Fiddler Options > HTTPS and ticking the Decrypt HTTPS Traffic box

Monitoring iPad traffic with Fiddler 2

1. Tools > Fiddler Options > Allow remote computers to connect

2. Accept generic SSL certficate and restart fiddler

3. Make sure Fiddler is set to capture traffic

Install Certifcate Maker
To resolve the incompatibility, you may replace Fiddler's default certificate generator. Download and install the new Certificate Maker and restart Fiddler.

1. FiddlerCertMaker.exe

2. When initially doing this had installed certificate without using FiddlerCertMaker.exe

3. How to uncheck and delete installed cert, closed Fiddler, ran FiddlerCertMaker.exe, started Fiddler

4. After all that re-added the certificate again

Setup iPad to use Proxy

1. Click on your Wifi Setup

2. DHCP, Manual

3. Enter the IP of your computer and Port 8888

Save session as:
httpArchive v1.2
and Fiddler Session Archive

Posted on

Changes to OLCI tables

You will need to update the following items when making changes to OLCI.
See sample script.

-- CHECKIN_PASSENGER TABLE
ALTER TABLE WEB_OWNER.CHECKIN_PASSENGER

-- CHECKIN_PASSENGER_DELETED TABLE
ALTER TABLE WEB_OWNER.CHECKIN_PASSENGER_DELETED

-- CHECKIN_PASSENGER_ARC TABLE
ALTER TABLE  WEB_ARCHIVE.CHECKIN_PASSENGER_ARC

-- CHECKIN_PASSENGER_DELETED_ARC TABLE
ALTER TABLE WEB_ARCHIVE.CHECKIN_PASSENGER_DELETED_ARC

-- CHECKIN_DELETE_TRG TRIGGER
TRIGGER "WEB_OWNER"."CHECKIN_DELETE_TRG"
ALTER TRIGGER "WEB_OWNER"."CHECKIN_DELETE_TRG" ENABLE;

-- CHECKIN_ARCHIVE_PROCESS
PACKAGE BODY CHECKIN_ARCHIVE_PROCESS is

Posted on

CCL API vs POLAR API

From: jchandran@princesscruises.com [mailto:jchandran@princesscruises.com]
Sent: Monday, October 29, 2012 2:30 PM
To: Augustine, Anila (HAL)
Cc: Davidson, Larry (PCL)
Subject: Re: CCL API vs POLAR API

Hi Anila,

CCL API/ Corporate API are the set of messages that follows Carnival guidelines. These are the message structures used by all the API  partners (like AMADEUS) and brands (like HAL) . To change these messages, we have to get approval from Carnival.

Princess used to use (continuing to use) certain messages before the introduction of CCL API. These are Polar API messages and doesn't follow corporate API standards. These messages are internal to Princess and does not affect other cruise lines or API partners.

Larry,

Please correct me if I am wrong.

Thanks,
Jathin Chandran
Corporate API Systems
IT, Princess Cruises
(661) 284 4377

Posted on

Linux search commands

Use the following two command to research program usage in Linux:

The following will show you the location of the program you run from the command/defined:
$which command-to-lookup

The following will show you where the basic places for the command happen to be:
$locate command-to-lookup

 

Posted on

Siebel Timeouts

From: Augustine, Anila (HAL)
Sent: Friday, October 19, 2012 9:02 AM
To: Fillman, Eric (HAL); Klein, Brian (HAL); Ruckman, Maurice (HAL); Thompson, Sonya (HAL); Willows, Aaron (HAL)
Subject: FW: My Seabourn

All,

FYI below. In the event I don’t, one you please forward the Siebel time out as the occur to this dist list: HAL DistList: CRM Prod Team. This is only temporary until we have the front end notification in place.

I will copy you in my emails to them so its not duplicated. Please cc me in case you send it.

Thanks
Anila

---

From: halprdjbs02.hq.halw.com@hollandamerica.com [mailto:halprdjbs02.hq.halw.com@hollandamerica.com]
Sent: Wednesday, October 17, 2012 10:48 AM
To: HAL DistList: IT Application Info
Subject: Siebel operation timed out

There is a problem with guest preference lookup. Siebel is timing out

格浴浸湬㩳潴扭祯∽瑨灴⼺戯慥湴歩潳瑦慷敲挮浯琯浯潢≹砠汭獮猺穩㵥栢瑴㩰⼯敢瑡楮獫景睴牡⹥潣⽭潴扭祯猯穩≥砠汭獮氺湩㵫栢瑴㩰⼯敢瑡楮獫景睴牡⹥潣⽭潴扭祯氯湩≫㰾潢祤䘾潲㩭䄠杵獵楴敮‬湁汩⁡䠨䱁
戼㹲敓瑮›牆摩祡‬捏潴敢⁲㤱‬〲㈱㤠〺′䵁戼㹲潔›楆汬慭Ɱ䔠楲⁣䠨䱁㬩䬠敬湩‬牂慩䠨䱁㬩删捵浫湡‬慍牵捩⁥䠨䱁㬩吠潨灭潳Ɱ匠湯慹⠠䅈⥌※楗汬睯ⱳ䄠牡湯⠠䅈⥌戼㹲畓橢捥㩴䘠㩗䴠⁹敓扡畯湲戼㹲戼㹲汁ⱬ戼㹲戼㹲奆⁉敢潬⹷䤠桴⁥癥湥⁴⁉潤馀ⱴ漠敮礠畯瀠敬獡⁥潦睲牡⁤桴⁥楓扥汥琠浩⁥畯⁴獡琠敨漠捣牵琠桴獩搠獩⁴楬瑳›䅈⁌楄瑳楌瑳›剃⁍牐摯吠慥⹭吠楨⁳獩漠汮⁹整灭牯牡⁹湵楴敷栠癡⁥桴⁥牦湯⁴湥⁤潮楴楦慣楴湯椠汰捡⹥戼㹲戼㹲⁉楷汬挠灯⁹潹⁵湩洠⁹浥楡獬琠桴浥猠瑩⁳潮⁴畤汰捩瑡摥‮汐慥敳挠⁣敭椠慣敳礠畯猠湥⁤瑩㰮牢㰾牢吾慨歮㱳牢䄾楮慬戼㹲戼㹲ⴭ㰭牢㰾牢䘾潲㩭㰠⁡瑳汹㵥挢汯牯⌺㐳㔶㑁•牨晥∽慨灬摲扪び⸲煨栮污⹷潣䁭潨汬湡慤敭楲慣挮浯㸢慨灬摲扪び⸲煨栮污⹷潣䁭潨汬湡慤敭楲慣挮浯⼼㹡嬠愼猠祴敬∽潣潬㩲㌣㘴䄵∴栠敲㵦洢楡瑬㩯慨灬摲扪び⸲煨栮污⹷潣䁭潨汬湡慤敭楲慣挮浯㸢慭汩潴栺污牰橤獢㈰栮⹱慨睬挮浯桀汯慬摮浡牥捩⹡潣㱭愯崾㰠牢匾湥㩴圠摥敮摳祡‬捏潴敢⁲㜱‬〲㈱ㄠ㨰㠴䄠㱍牢吾㩯䠠䱁䐠獩䱴獩㩴䤠⁔灁汰捩瑡潩湉潦戼㹲畓橢捥㩴匠敩敢灯牥瑡潩楴敭⁤畯㱴牢㰾牢吾敨敲椠⁳⁡牰扯敬楷桴朠敵瑳瀠敲敦敲据⁥潬歯灵‮楓扥汥椠⁳楴業杮漠瑵戼㹲⼼潢祤㰾栯浴㹬
Posted on

POLAR Training Manuals

Useful libraries in eCat Polar Training Manuals:
http://ecatstand.flagship.hal.com/trainingtools/PolarTrainingManuals/Forms/AllItems.aspx

• POLAR – AVAL Availability and Add Booking Functions
http://ecatstand.flagship.hal.com/trainingtools/PolarTrainingManuals/Forms/AllItems.aspx?RootFolder=%2ftrainingtools%2fPolarTrainingManuals%2fPOLAR%20%2d%20AVAL%20Availability%20and%20Add%20Booking%20Functions&FolderCTID=&View=%7bFDD24CB4%2dDD0A%2d48C0%2dA1C6%2d9041BE05CADE%7d

• POLAR – CBOK Existing Booking Functions
http://ecatstand.flagship.hal.com/trainingtools/PolarTrainingManuals/Forms/AllItems.aspx?RootFolder=%2ftrainingtools%2fPolarTrainingManuals%2fPOLAR%20%2d%20CBOK%20Existing%20Booking%20Functions&FolderCTID=&View=%7bFDD24CB4%2dDD0A%2d48C0%2dA1C6%2d9041BE05CADE%7d

Posted on

UTF-8 Encoding

Trying to diagnose problem with UTF-8 encoding on the batch jobs, previous notes from WebSphere are as follows:

From: Ruckman, Maurice (HAL)
Sent: Tuesday, March 27, 2012 4:55 PM
To: jlindesm@redhat.com
Cc: 'Guillaume Radde'; Thompson, Sonya (HAL); Bojja, Sridhar (HAL Contractor); Phatak, Sheetal (HAL); Fillman, Eric (HAL)
Subject: JBboss encoding for UTF-8

In WebSphere we did this to make sure the application used UTF-8 encoding by default

CONFIGURING APPLICATION SERVERS FOR UCS TRANSFORMATION FORMAT, TO SUPPORT UTF-8 ENCODING

1. Click Servers, "Application servers"
1a. Click "server1" link
1b. Configuration tab, "Java and Process Management", "Process Definition"
1c. "Java Virtual Machine"

2. In section "Generic JVM arguments", enter the following parameter
"-Dclient.encoding.override=UTF-8 -Ddefault.client.encoding=UTF-8"

Thanks,

Maurice Ruckman
Voice: (206) 626-7497 x67497
Cellular: (206) 650-7576