CLS Solutions Technology Blog

Google Health, a first look
2/28/2008 06:30:00 AM Posted by Marissa Mayer, VP, Search & User ProductsIt’s been a busy week for the Google Health team. Last week we announced our partnership and pilot with the Cleveland Clinic. This week, the team has been at the HIMSS (Healthcare Information and Management Systems Society) conference in Orlando, Florida, where Eric Schmidt gave the closing keynote. Eric’s keynote marks the first time we’ve talked publicly about the product we’ve been designing and building. His talk also offered a deeper view into our overall health strategy. (Watch the video.)

Google Health aims to solve an urgent need that dovetails with our overall mission of organizing patient information and making it accessible and useful. Through our health offering, our users will be empowered to collect, store, and manage their own medical records online.For the healthcare industry, online personal health records (PHRs) aren’t a new idea and, in some cases, online PHRs already exist for patients. Here’s what we think sets Google Health apart:

Privacy and Security – Due to the sensitive and personal nature of the data that will be stored in Google Health, we need to conduct our health service with the same privacy, security, and integrity users have come to expect in all our services. Google Health will protect the privacy of your health information by giving you complete control over your data. We won’t sell or share your data without your explicit permission. Our privacy policy and practices have been developed in thoughtful collaboration with experts from the Google Health Advisory Council.

Platform – One of the most exciting and innovative parts of Google Health is our platform strategy. We’re assembling a directory of third-party services that interoperate with Google Health. Right now, this means you’ll be able to automatically import information such as your doctors’ records, your prescription history, and your test results into Google Health in order to easily access and control your data. Later, this platform strategy will mean that you will be able to interact with services and tools easily, and will be able to do things like schedule appointments, refill prescriptions, and start using new wellness tools.

Portability – Our Internet presence ultimately means that through Google Health, you will be able to have access and control over your health data from anywhere. Through the Cleveland Clinic pilot, we have already found great use-cases in which, for example, people spend 6 months of the year in Ohio, and 6 months of the year in Florida or Arizona, and will now be able to move their health data between their various health providers seamlessly and with total control. Previously, this would have required carrying paper records back and forth. With Google Health, the user can simply import the data from each medical facility and then choose to share it with the other facilities. It’s advances in data portability like this that we think can really make a difference in the quality of healthcare. The clearer and more comprehensive the information regarding your health becomes, the better your care will be.

User focus – We aren’t doctors or healthcare experts, but one thing Google can create is a clean, easy-to-use user experience that makes managing your health information straightforward and easy. We’re still iterating and testing our user interface, but here is what the welcome screen looks like:Here is a screenshot deeper in the application:

We’re proud of the product that we’ve designed and are continuing to build, but recognize that we are just at the initial stages of our “launch early and iterate” strategy. We look forward to the feedback we will receive from our Cleveland Clinic pilot, from all of you, and from the initial users of our service when we make it publicly available in the coming months.

Free! Why $0.00 Is the Future of Business – wired magazine

What Mead understood is that a psychological switch should flip as things head toward zero. Even though they may never become entirely free, as the price drops there is great advantage to be had in treating them as if they were free. Not too cheap to meter, as Atomic Energy Commission chief Lewis Strauss said in a different context, but too cheap to matter. Indeed, the history of technological innovation has been marked by people spotting such price and performance trends and getting ahead of them.

From the consumer’s perspective, though, there is a huge difference between cheap and free.

The huge psychological gap between “almost zero” and “zero” is why micropayments failed.

To follow the money, you have to shift from a basic view of a market as a matching of two parties — buyers and sellers — to a broader sense of an ecosystem with many parties, only some of which exchange cash.

The most common of the economies built around free is the three-party system. Here a third party pays to participate in a market created by a free exchange between the first two parties.

They’re not selling papers and magazines to readers, they’re selling readers to advertisers.

“Freemium”What’s free: Web software and services, some content. Free to whom: users of the basic version.

But for digital products, this ratio of free to paid is reversed. A typical online site follows the 1 Percent Rule — 1 percent of users support all the rest. In the freemium model, that means for every user who pays for the premium version of the site, 99 others get the basic free version. The reason this works is that the cost of serving the 99 percent is close enough to zero to call it nothing.

You can get free porn if you solve a few captchas, those scrambled text boxes used to block bots. What you’re actually doing is giving answers to a bot used by spammers to gain access to other sites — which is worth more to them than the bandwidth you’ll consume browsing images.
genius!

Read your college textbook and it’s likely to define economics as “the social science of choice under scarcity.” The entire field is built on studying trade-offs and how they’re made. Milton Friedman himself reminded us time and time again that “there’s no such thing as a free lunch.
“But Friedman was wrong in two ways. First, a free lunch doesn’t necessarily mean the food is being given away or that you’ll pay for it later — it could just mean someone else is picking up the tab. Second, in the digital realm, as we’ve seen, the main feedstocks of the information economy — storage, processing power, and bandwidth — are getting cheaper by the day. Two of the main scarcity functions of traditional economics — the marginal costs of manufacturing and distribution — are rushing headlong to zip. It’s as if the restaurant suddenly didn’t have to pay any food or labor costs for that lunch.

ADT Interface
TASK – Hours
Planning (includes spec review) 8
Development 6
Functional Testing 8
Integrated Testing 10
Go-live
Prep 4
Support 4
Total Hours 50

Unidirectional Orders Interface
Planning (includes spec review) 15
Development 45
Functional Testing 24
Integrated Testing 60
Go-live
Prep 12
Support 12
Total Hours 168

Bidirectional Orders Interface
Planning (includes spec review) 35
Development 85
Functional Testing 48
Integrated Testing 120
Go-live
Prep 20
Support 20
Total Hours 328

Results Interface
Planning (includes spec review) 15
Development 45
Functional Testing 24
Integrated Testing 60
Go-live
Prep 12
Support 12
Total Hours 168

Charge Interface (HL7)
Planning (includes spec review) 6
Development 4
Functional Testing 6
Integrated Testing 2
Go-live
Prep 4
Support 2
Total Hours 24

Charge Interface (Non-HL7)
Planning (includes spec review) 30
Development 25
Functional Testing 12
Integrated Testing 6
Go-live
Prep 4
Support 4
Total Hours 81

Miscellaneous Data Interfaces
Planning (includes spec review) 25
Development 40
Functional Testing 20
Integrated Testing 20
Go-live
Prep 6
Support 4
Total Hours 115

VI: (yank/paste)
1Y,2Y,3Y,etc
P

VI: (Remove ^M’s)
:%s/{CTRL-V+CTRL-M}//g

CRIMPSON: (matching brackets)
Begin-> CTRL + [
End-> CTRL + ]

ps -ef | egrep -v “stime”| sort +3 -r | head -n 15

If you need to quickly check an external IP & port w/o sending anything..

/home/egatetst/scripts > ksh i-tcp-param.sh 170.999.0.67 3111
passed

/home/egatetst/scripts > ksh i-tcp-param.sh 170.999.0.67 3112
i-tcp-param.sh[3]: /dev/tcp/170.999.0.67/3112: cannot create
failed

>>>>START CODE<<<<<<<<<<<<<<<<<<<<
#!/usr/bin/ksh
# example : ksh i-tcp-param.sh 170.999.0.67 8888
if [ exec 3<> /dev/tcp/$1/$2 ]
then
echo “passed”
else
echo “failed”
fi
>>>>>>>>>END CODE<<<<<<<<<<<< *NOTE: if this hangs it means that theres ‘no response’ from IP

These 2 files consisting of 10 lines of code allows you to rename a string within the whole file system. I’ve used this when creating new development environments and limited changes that pertain to only one set of directories. It keeps a record of changed files so you can double check that it doesnt do anything unexpected. It recreates the files,so permission might need to be changed back to the originals.
Note:
-$1 is the parameter search string to change
-*sh is the file filter criteria
-String1 is the string to change [same as $1 above]
-String2 is the desired new string name

f_find_it.sh
find . -name ‘*sh’ -exec grep -l “$1” {} \; > files.txt
ksh f_callsed.sh files.txt
ksh work1
rm work.1

f_callsed.sh
let x=1
while read -u3 f1; do
printf “sed -e ‘s/String1/String2/g’ $f1 > work.$x\n” >>work1
printf “cp work.$x $f1\n”>>work1
cat work1
done 3<$1

HL7 Event Types

A01 ADT/ACK – Admit/visit notification
A02 ADT/ACK – Transfer a patient
A03 ADT/ACK – Discharge/end visit
A04 ADT/ACK – Register a patient
A05 ADT/ACK – Pre-admit a patient
A06 ADT/ACK – Change an outpatient to an inpatient
A07 ADT/ACK – Change an inpatient to an outpatient
A08 ADT/ACK – Update patient information
A09 ADT/ACK – Patient departing – tracking
A10 ADT/ACK – Patient arriving – tracking
A11 ADT/ACK – Cancel admit/visit notification
A12 ADT/ACK – Cancel transfer
A13 ADT/ACK – Cancel discharge/end visit
A14 ADT/ACK – Pending admit
A15 ADT/ACK – Pending transfer
A16 ADT/ACK – Pending discharge
A17 ADT/ACK – Swap patients
A18 ADT/ACK – Merge patient information
A19 QRY/ADR – Patient query
A20 ADT/ACK – Bed status update
A21 ADT/ACK – Patient goes on a leave of absence
A22 ADT/ACK – Patient returns from a leave of absence
A23 ADT/ACK – Delete a patient record
A24 ADT/ACK – Link patient information
A25 ADT/ACK – Cancel pending discharge
A26 ADT/ACK – Cancel pending transfer
A27 ADT/ACK – Cancel pending admit
A28 ADT/ACK – Add person information
A29 ADT/ACK – Delete person information
A30 ADT/ACK – Merge person information
A31 ADT/ACK – Update person information
A32 ADT/ACK – Cancel patient arriving – tracking
A33 ADT/ACK – Cancel patient departing – tracking
A34 ADT/ACK – Merge patient information – patient ID only
A35 ADT/ACK – Merge patient information – account number only
A36 ADT/ACK – Merge patient information – patient ID and account number
A37 ADT/ACK – Unlink patient information
A38 ADT/ACK – Cancel pre-admit
A39 ADT/ACK – Merge person patient ID
A40 ADT/ACK – Merge patient patient identifier list
A41 ADT/ACK – Merge account – patient account number
A42 ADT/ACK – Merge visit – visit number
A43 ADT/ACK – Move patient information patient identifier list
A44 ADT/ACK – Move account information – patient account number
A45 ADT/ACK – Move visit information – visit number
A46 ADT/ACK – Change patient ID
A47 ADT/ACK – Change patient identifier list
A48 ADT/ACK – Change alternate patient ID
A49 ADT/ACK – Change patient account number
A50 ADT/ACK – Change visit number
A51 ADT/ACK – Change alternate visit ID
A60 ADT/ACK – Update Allegy Information

RE: [STC-User] Re: [UD] – eGate: A Christmas Carol

Twas the night before Christmas, and all through the schema,
red flashing ALERTs interrupted my dreama.

All the eWays were hung by the network crash!” Operations declared.
In hopes that an engineer would soon be there.

And what to my horrified eyes should appear?
Eight network engineers saying ‘You’ve got to get all new gear.’

The engineers were snuggled asleep in their cubes
While numerous Monk exceptions danced across the tubes.

And the network manager in his coat and I in my car
Were just rushing out for a drink in the bar.

When what to my I-Pod plugged ears should break through
But a pager, a cell phone, and my Blackberry, too.

Down Epic and Siemens and even Transcription
No interfaces are moving – not even a smidgeon.

Then my manager said with no trace of a grin
Get this fixed soon or your job here will end.

I turned the car around as fast as I could
and headed back work, just as I always would

When I got back work, what did I hear
But the generator a blasting and sounding so clear

Then, from up above – a voice some what near –
he seemed to asking if he was really here.

On Cerner, and Sunquest, Pyxis you fool –
pick up your ACK times or I’ll call NEO-tool.

Now ref-labs and remote hosts – run down your VPN
or I’ll tell your bosses you’ve been into the gin.

Get IDX, and Invision and EPIC and jool –
the bucks need to flow – so jump through the snow

My head started hurting and I thought in a blink –
things could be worse – I could be using OpenLink.

But now it is dark and getting quite late
I thank the world that I have eGate.

With a little tweak here and promote to runtime
Everything’s fixed, and I’m feeling fine.

The boss is now happy – he gives me a cheer
But I’d much rather have a six pack of beer.

Working with CLOBs has been very difficult. The task was to extract all unique messages that were in LDR2 and not in LDR into a UNIQUE table.
Set commands such as,MINUS, INTERSECT, =, etc, won’t work with CLOBs datatypes. But using dbms_lob.getlength, dbms_lob.Compare, and dbms_Utility.Get_hash_value. This sql OUTER-JOIN finally worked:

insert into seebeyond.RAD_MESSAGES_UNIQUE (SELECT seebeyond.RAD_MESSAGES_LDR2.MESSAGES, seebeyond.RAD_MESSAGES_LDR2.ID FROM seebeyond.RAD_MESSAGES_LDR2 LEFT OUTER JOIN seebeyond.RAD_MESSAGES_LDR ON (seebeyond.RAD_MESSAGES_LDR2.HASH = seebeyond.RAD_MESSAGES_LDR.HASH) AND (seebeyond.RAD_MESSAGES_LDR2.MSGLEN = seebeyond.RAD_MESSAGES_LDR.MSGLEN) AND (dbms_lob.Compare(seebeyond.RAD_MESSAGES_LDR2.MESSAGES,seebeyond.RAD_MESSAGES_LDR.MESSAGES)=0) WHERE seebeyond.RAD_MESSAGES_LDR.ID IS NULL)

SQL> select count(*) from RAD_MESSAGES_LDR2;

COUNT(*)
———-
744923

SQL> select count(*) from RAD_MESSAGES_LDR;

COUNT(*)
———-
713316

SQL> select count(*) from RAD_MESSAGES_UNIQUE;

COUNT(*)
———-
31624

find . -name “PLW_TCPIN*” -exec grep -l “$1” {} \; (finds file & string in file)
find . -name “*core*” | xargs ls -l (finds cores and their sizes)
find . -size +100000 -print (find files over 1 gig)

To Rename all .jpeg to .jpg:
for file in *.jpeg; do mv “$file” “${file%.jpeg}.jpg”; done

sed G
sed ‘s/.$//’ # assumes that all lines end with CR/LF
sed ‘s/^M$//’ # in bash/tcsh, press Ctrl-V then Ctrl-M
sed ‘s/\x0D$//’ # gsed 3.02.80, but top script is easier
sed “s/\r//” infile >outfile # UnxUtils sed v4.0.7 or higher
sed ‘s/^[ \t]*//’ # see note on ‘\t’ at end of file
sed ‘s/foo/bar/’ # replaces only 1st instance in a line
sed ‘s/foo/bar/4’ # replaces only 4th instance in a line
sed ‘s/foo/bar/g’ # replaces ALL instances in a line
sed ‘s/\(.*\)foo\(.*foo\)/\1bar\2/’ # replace the next-to-last case
sed ‘s/\(.*\)foo/\1bar/’ # replace only the last case
sed ‘/baz/s/foo/bar/g’

Miscellaneous issues when upload/downloading from Oracle.

SPOOLING:
When downloading/Spooling, large fields (Clobs/Memo) were being truncated. Had to SQL>Show all. Linesize,long,longchunksize were defaulting to 80-increased these.

SQLLDR:
sqlldr scott/tiger@LAWSON2 log=log.txt control=loader.ctl

[loader.ctl]
load data
infile ‘c:\merged.dat’
into table seebeyond.RAD_MESSAGES_LDR
fields terminated by “abcZ123” optionally enclosed by “”
(MESSAGES CHAR(100000))

*To create One table from another: CREATE TABLE ZZZ AS SELECT * FROM AAA

*Set commands (UNION,etc) cannot be used in Clob/Memo fields

Subject: IMPORTANT: New Email Address for Java CAPS Support

Dear valued customer,
We would like to take this time to inform you that we are disabling some of our old SeeBeyond email addresses. We ask that you no longer send Support emails to support@seebeyond.com or SeeBeyond-PoweringeBusinesses2@SeeBeyond.com. These addresses will be disabled effective March 31, 2007.We recommend that you start using caps-support@sun.com from this point forward.Please do not hesitate to contact us if you require further clarification. Thank you for your understanding.
-RegardsJava CAPS Support

After discovering the the search engines are very limited in returning searches for free-reprint articles. I created a new tool called ArticleBankSearch located on articlewarehouse.com.

I experimented with the limited nature of google advanced searches to filter only the article banks. Google is limited to only one domain in their advanced interface, however it is possible to use a complex string of ‘OR sites’ to filter by multiple domains, but this is limited to just 6-7 domains.

I found a better domain filter using GigaBlast. GigaBlast.com has a tool called ‘custom topic search’ http://www.gigablast.com/cts.html which allows up 200 domains to be used in a single search query. I’ve added 100+ of the top article banks to this single query. Now, when someone is looking specifically for free-reprint articles on the internet, they won’t get licensed articles, and other non-relevant pages.

Have you tried this tool? Like to see some more features? Comments welcome..

UB was once again indexed/spidered by G 08′

UB website was scaled back to purely informational 07′

UB Upgrades were discontinued 06′

We have added a cool rss news feature for retrieving the latest news on the various airlines compliments of BigBold.com. An example is on the home page called ‘Latest Delta Airlines News ‘ and it’s on all the airline specific news pages. Do to some webhost issues the newsletter has been on hold for the time being. -05

Moved AWH to hostgator webhost and changed to ArticleDashboard CMS. -11/08′

10,000+ Copyright Free Articles & 4,000+ Licensed Articles Added by over 5000 Authors over the past 4 years. -08′

I’ve removed the fastclick banners located in the headers of articlewarehouse.com, they have been replaced with a google search. Also the date shows now at the top.
Most websites seem to have a search box located at the very top, so we’ll see if more searches are done when its at the top.-06′
-Carl

This is a tech blog from CLS Solutions developers covering various projects, websites, and other useful information to members, users, and guests. Members and guests may post comments.

This announcement establishes the timeline and dates for the End of Service Life for Java CAPS release 5.1.2.

This announcement applies only to Java CAPS release 5.1.2. Other products currently on Sun’s price-list including ICAN J2EE 5.0.5, Java CAPS 6, Java CAPS 5.1.3, ICAN SRE 5.0.5, e*Gate 4.5.3, and ICAN TRE 5.0.1 continue to be supported with no current EOSL announcements having been made.

Products entering EOSL:

The following components of Java CAPS 5.1.2 are beginning the End Of Service Life process (EOSL). All products on this EOSL announcement already have direct replacements available.

eGate Integrator 5.1.2

eInsight Business Process Manager 5.1.2

eVision Studio 5.1.2

eBAM Studio 5.1.2

eTL Integrator 5.1.2

eView Studio 5.1.2

Sun Java System Portal Server 6.3 5.1.2

Sun Java System Portal Server 7 5.1.2

eIndex Single Patient View 5.1.2

Alert Agent 5.1.2

Batch eWay 5.1.2

CICS eWay 5.1.2

COBOL CopyBook Converter 5.1.2

COM/DCOM eWay 5.1.2

DB2 eWay 5.1.2

DB2 Connect eWay 5.1.2

eGate API Kit 5.1.2

e-Mail eWay 5.1.2

eWay Development Kit 5.1.2

HL7 OTD Library 5.1.2

HTTPS eWay 5.1.2

IMS eWay 5.1.2

Informix Database eWay 5.1.2

JDBC/ODBC eWay 5.1.2

LDAP eWay 5.1.2

Lotus Notes/Domino eWay 5.1.2

MSMQ eWay 5.1.2

Oracle eWay 5.1.2

Oracle Applications eWay 5.1.2

PeopleSoft eWay 5.1.2

SAP ALE eWay 5.1.2

SAP BAPI eWay 5.1.2

Seagull Screen Access eWay 5.1.2

Siebel EAI eWay 5.1.2

SNA eWay 5.1.2

SNMP Agent 5.1.2

SQL Server eWay 5.1.2

Sun Java System Application Server eWay 5.1.2

Swift Alliance Gateway eWay 5.1.2

Swift OTD Library 5.1.2

Sybase eWay 5.1.2

TCP/IP eWay 5.1.2

TCP/IP HL7 eWay 5.1.2

VSAM eWay 5.1.2

WebLogic App Server eWay 5.1.2

WebSphere MQ eWay 5.1.2

Upgrade plan:

Existing customers using Java CAPS 5.1.2 are encouraged to upgrade to newer releases of Java CAPS. The GA releases available as of the date of this announcement are Java CAPS 6 and Java CAPS 5.1.3. However as Java CAPS 5.1.2 customers will continue to have support for some time (see section “Key dates”), they can evaluate and plan to move to a more recent version on their own schedule. Upgrade information is available from the Java CAPS documentation which can be accessed at: http://developers.sun.com/docs/javacaps/upgrading/index.html. More details on the new release can be found at http://developers.sun.com/docs/javacaps/index.jsp.

Key dates:

EOSL of Java CAPS 5.1.2 will follow Sun’s EOSL policy which can be found at http://www.sun.com/service/eosl/. Products included in this announcement will be supported in two phases. The first phase is a full support phase and during this phase customers will continue to receive bug fix support from now until December 26, 2009 on which date full fix support will cease. After this date these products will enter the second and final phase of limited support for four years. In the second phase, customers will not be entitled to submit bugs or to receive new patches from Sun, however existing patches will be provided. The date at which limited support will cease is December 26, 2013.

Fix support ends: December 26, 2009
Limited support ends: December 26, 2013

Have any questions or comments? Any readers, users, members, or customers are welcome. Post any comments here….

**EOL Announcement for Java CAPS releases 5.1.0 and 5.1.1**

This announcement establishes the timeline and dates for the End of Service Life for Java CAPS releases 5.1.0 and 5.1.1.

This announcement does not apply to the currently available products/versions on Sun’s current price-list. Products currently on Sun’s price-list including Java CAPS 5.1.3, Java CAPS 5.1.2, ICAN J2EE 5.0.5, ICAN SRE 5.0.5, e*Gate 4.5.3, and ICAN TRE 5.0.1 continue to be supported with no current EOL announcements having been made.

Products entering EOL:

The following components of Java CAPS 5.1.0 are beginning the End Of Life process (EOL). All products on this EOL announcement already have direct replacements available.

No. Product Name

eGate Integrator 5.1.0
eInsight Business Process Manager 5.1.0
eVision Studio 5.1.0
eBAM Studio 5.1.0
eTL Integrator 5.1.0
eView Studio 5.1.0
eIndex Single Patient View 5.1.0
Alert Agent 5.1.0
Batch eWay 5.1.0
CICS eWay 5.1.0
COBOL CopyBook Converter 5.1.0
COM/DCOM eWay 5.1.0
DB2 eWay 5.1.0
DB2 Connect eWay 5.1.0
eGate API Kit 5.1.0
e-Mail eWay 5.1.0
HL7 OTD Library 5.1.0
HTTPS eWay 5.1.0
IMS eWay 5.1.0
JDBC/ODBC eWay 5.1.0
LDAP eWay 5.1.0
Oracle eWay 5.1.0
PeopleSoft eWay 5.1.0
SAP ALE eWay 5.1.0
SAP BAPI eWay 5.1.0
Siebel EAI eWay 5.1.0
SNA eWay 5.1.0
SNMP Agent 5.1.0
SQL Server eWay 5.1.0
Sun Java System Application Server eWay 5.1.0
Swift OTD Library 5.1.0
Sybase eWay 5.1.0
TCP/IP eWay 5.1.0
TCP/IP HL7 eWay 5.1.0
VSAM eWay 5.1.0
WebLogic App Server eWay 5.1.0
WebSphere MQ eWay 5.1.0
The following components of Java CAPS 5.1.1 are also in the End Of Life process (EOL). All products on this EOL announcement already have direct replacements available.

No. Product Name
eGate Integrator 5.1.1
eInsight Business Process Manager 5.1.1
eVision Studio 5.1.1
eBAM Studio 5.1.1
eTL Integrator 5.1.1
eView Studio 5.1.1
eIndex Single Patient View 5.1.1
Alert Agent 5.1.1
Batch eWay 5.1.1
CICS eWay 5.1.1
COBOL CopyBook Converter 5.1.1
COM/DCOM eWay 5.1.1
DB2 eWay 5.1.1
DB2 Connect eWay 5.1.1
eGate API Kit 5.1.1
e-Mail eWay 5.1.1
eWay Development Kit 5.1.1
HL7 OTD Library 5.1.1
HTTPS eWay 5.1.1
IMS eWay 5.1.1
Informix Database eWay 5.1.1
JDBC/ODBC eWay 5.1.1
LDAP eWay 5.1.1
Lotus Notes/Domino eWay 5.1.1
MSMQ eWay 5.1.1
Oracle eWay 5.1.1
Oracle Applications eWay 5.1.1
PeopleSoft eWay 5.1.1
SAP ALE eWay 5.1.1
SAP BAPI eWay 5.1.1
Seagull Screen Access eWay 5.1.1
Siebel EAI eWay 5.1.1
SNA eWay 5.1.1
SNMP Agent 5.1.1
SQL Server eWay 5.1.1
Sun Java System Application Server eWay 5.1.1
Swift OTD Library 5.1.1
Sybase eWay 5.1.1
TCP/IP eWay 5.1.1
TCP/IP HL7 eWay 5.1.1
VSAM eWay 5.1.1
WebLogic App Server eWay 5.1.1
WebSphere MQ eWay 5.1.1
Upgrade plan:

Existing customers using Java CAPS 5.1.0 and 5.1.1 are encouraged to upgrade to newer releases of Java CAPS. The current GA release available as on the date of this announcement is Java CAPS 5.1.3. However as Java CAPS 5.1.0 customers will continue to have support for some time (see section Key Dates), they can evaluate using Java CAPS releases that are on the road map, such as Java CAPS 5.2 scheduled for release in Q4FY08 (i.e. Q2CY08) or a 5.2+ release.

Upgrading from Java CAPS 5.1.0, 5.1.1, or 5.1.2 to 5.1.3 may be performed as an in-place upgrade or via a fresh install and export/import. Upgrade information is available from Java CAPS documentation including the 5.1.3 installation guide which can be found at http://docs.sun.com/app/docs/doc/820-0938. Users will have to refer to individual product documentation for upgrade information as there may be product-specific upgrade requirements. Please refer to Java CAPS 5.1.3 documentation for required products located at http://docs.sun.com/app/docs/coll/1601.3.

Key dates:

EOL of Java CAPS 5.1.0 will have same EOL date as Java CAPS 5.1.1. Products included in this announcement will be supported in two phases. The first phase is a full support phase and during this phase customers will continue to receive bug fix support from now until November 30, 2008 on which date full fix support will cease. After this date these products will enter the second and final limited support phase for limited support for four years. In the second phase, customers will not be entitled to submit bugs or to receive new patches from Sun. The date at which limited support will cease is November 30, 2012.

Full support ends: Nov 30, 2008
Limited support ends: Nov 30, 2012

FAQ

Question:
Why is Java CAPS release 5.1.0 and 5.1.1 beginning the EOL process?

Answer:
Sun is announcing EOL for earlier releases because there are straight-forward upgrades for each of the EOL’d products and versions. The EOL support period gives adequate time for customers to move to an actively supported product/version. This action of EOL-ing older releases enables Sun to focus resources on enhancing our products to meet evolving business needs.

This announcement establishes the timeline and dates for the End of Service Life for a subset of prior versions of Sun SeeBeyond(tm) products. This announcement does not apply to the currently available products/versions on Sun’s current price-list.Older releases of Sun SeeBeyond ™ products (e*Gate(tm) 4.0, 4.1, 4.1.1 and 4.1.2, e*Gate 4.5.0, 4.5.1 and 4.5.2, ICAN(tm) J2EE 5.0.0 through 5.0.4, ICAN SRE 5.0.0 through 5.0.4, and ICAN TRE 5.0.0 are beginning the End Of Life process (EOL). Products currently on Sun’s price-list including ICAN J2EE 5.0.5, Java CAPS 5.1.x, ICAN SRE 5.0.5, e*Gate 4.5.3, and ICAN TRE 5.0.1 continue to be supported with no current EOL announcements having been made.All versions of SeeBeyond software that are announcing EOL already have direct replacements available.* e*Gate 4.x users can upgrade to ICAN SRE 5.0.5* ICAN J2EE users can upgrade to ICAN J2EE 5.0.5 or Java CAPS ™ 5.1.3* ICAN TRE 5.0.0 users can upgrade to ICAN TRE 5.0.1All customers are encouraged to upgrade to the latest applicable version to benefit from the fixes and enhancements made in those versions. Each of these upgrades have been successfully performed by many customers with little to no rework required during the upgrade.Products included in this announcement will continue to receive full fix support for 6 or 12 months. Products receiving full fix support for 6 months will receive phone only support for an additional 6 months after fix support ceases. Products receiving full fix support for 12 months will receive phone only support for an additional 12 months after fix support ceases.A summary of the products receiving support for 12 months is:* ICAN TRE 5.0.0* ICAN SRE 5.0.4* ICAN J2EE 5.0.4The date at which fix support will cease for 12 months support products is May 22, 2008. The date at which phone only support will cease is May 22, 2009.A summary of the products receiving support for 6 months is:* ICAN SRE 5.0.0, 5.0.1, 5.0.2, and 5.0.3* ICAN J2EE 5.0.0, 5.0.1, 5.0.2, and 5.0.3* e*Gate 4.0, 4.1, 4.1.1, 4.1.2, 4.5, 4.5.1, and 4.5.2The date at which fix support will cease for 6 months support products is November 22, 2007. The date at which phone only support will cease is May 22, 2008.The specific list of products and versions included in this announcement and which support category they are in are in the attached file.FAQQuestion:Why are the older Sun SeeBeyond products beginning the EOL process?Answer:Sun is announcing EOL for the older Sun SeeBeyond products because there are straight-forward upgrades for each of the EOL’d products and versions. The EOL support period gives adequate time for customers to move to an actively supported product/version. This action of EOL-ing several versions of the products is being taken so that Sun can focus resources on supporting and enhancing the current versions of products which are used by the vast majority of our customers.