headers
Dilip Agheda | 1 Jun 2005 16:43

Re: Digest Number 1209


I am looking for any POS based project specification. like complete 
integrated retail POS system. can anybody help?

regards,
Dilip

At 01:09 PM 25/05/2005 +0000, you wrote:
>There are 5 messages in this issue.
>
>Topics in this digest:
>
>       1. ISO93
>            From: austin aghedo <austin_aghedo@...>
>       2. Re: ISO93
>            From: Alejandro Revilla <apr@...>
>       3. Re: ISO93
>            From: "Thomas L. Kjeldsen" <tlk@...>
>       4. Re: ISO93
>            From: austin aghedo <austin_aghedo@...>
>       5. Re: ISO93
>            From: Alejandro Revilla <apr@...>
>
>
>________________________________________________________________________
>________________________________________________________________________
>
>Message: 1
>    Date: Tue, 24 May 2005 08:39:34 -0700 (PDT)
>    From: austin aghedo <austin_aghedo@...>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas L. Kjeldsen | 2 Jun 2005 00:25
Picon

Re: Channel debugging, hex-dump of raw messages

Thomas L. Kjeldsen wrote:
> 
> I can make hex-dumps of sample request messages from Q2 (connect without
> SSL to a listening netcat), but I find it a little harder to make
> complete hex-dumps of live response messages from the remote end. I'm
> thinking about making a wrapper for serverIn and serverOut and utilize
> the fact that my channel has to be connected/disconnected for each
> request/response set, but I feel this may be overkill.

FYI, I did a hack back then that will write raw message dumps in the
BaseChannel. Socket input and output data is written to files using
TeeInputStream and TeeOutStream found in a completely unrelated project
called morphis. You can get morphis.jar with the Tee* classes from
http://www.morphis.org.

Please note this should certainly not be used in a production system.

Thomas

  ----------

$Id: tlk-1117663590.diff,v 1.1 2005/06/01 22:06:32 tlk Exp $

Index: src/main/org/jpos/iso/BaseChannel.java
===================================================================
RCS file: /cvsroot/jpos/jpos/src/main/org/jpos/iso/BaseChannel.java,v
retrieving revision 1.54
diff -u -r1.54 BaseChannel.java
--- src/main/org/jpos/iso/BaseChannel.java	10 Dec 2004 00:26:56 -0000	1.54
+++ src/main/org/jpos/iso/BaseChannel.java	21 Dec 2004 11:21:44 -0000
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alejandro Revilla | 2 Jun 2005 03:59
Favicon
Gravatar

Re: Channel debugging, hex-dump of raw messages

> 
> FYI, I did a hack back then that will write raw message dumps in the
>
Hey, nice hack! we could put this in http://jpos.org/wiki/HOWTO

BTW, we have new Wiki (see http://jpos.org/wiki), poorly configured 
for now, but I hope you like it. Help is welcome. 

--Alejandro
Permalink | Reply | 0 comments |
headers
Sanjay Belagodu | 3 Jun 2005 23:49

RE: Question on Release 1.4.4

Hi,
I had a few more questions. I need to include a set of tables as a subfield
for a ISOfield. I am trying to define the XML for the ISO message.

1. Can I use GenericSubFieldPackager for this purpose
2. If one of the fields needs the length of the data in that table, do I
need to compute it externally ? or can I use any feature in JPOS

Please excuse me if these are elementary questions.
thanks in advance
sanjay

-----Original Message-----
From: Sanjay Belagodu 
Sent: Friday, May 27, 2005 4:23 PM
To: 'jpos-dev@...'
Subject: RE: [jpos-dev] Question on Release 1.4.4

thank you.

-----Original Message-----
From: Alejandro Revilla [mailto:apr@...]
Sent: Friday, May 27, 2005 4:14 PM
To: jpos-dev@...
Subject: Re: [jpos-dev] Question on Release 1.4.4

>
> 1. do we need to use the previous release of JPOS 1.4.2 ??
>
I'm afraid yes.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alejandro Revilla | 4 Jun 2005 00:18
Favicon
Gravatar

Re: Question on Release 1.4.4

> I had a few more questions. I need to include a set of tables as a subfield
> for a ISOfield. I am trying to define the XML for the ISO message.
> 
> 1. Can I use GenericSubFieldPackager for this purpose
>
I think so.

>
> 2. If one of the fields needs the length of the data in that table, do I
> need to compute it externally ? or can I use any feature in JPOS
> 
That's handled by the ISOFieldPackagers that you define for your
GenericSubFieldPackager. See src/main/org/jpos/iso/IF*L*.java
Permalink | Reply | 0 comments |
headers
Sanjay Belagodu | 4 Jun 2005 03:43

RE: Question on Release 1.4.4

I am still trying to figure out how to include more than one table, in one
field. I bought the JPOS programmers guide, got a some information on how to
create custom packager. Which I can use to create first Table, but could not
find out how I can add more Tables.

Below snippet shows the first Table(14) fields (Length Attribute, ...,
Amount). I need to add Tables 49... 
<isofieldpackager
      id="63"
      length="999"
      name="Tables 10-60"
      class="org.jpos.iso.IF_CHAR"
      packager="org.jpos.iso.packager.CustomTable14FieldPackager">
      <isofield
          	id="0"
          	length="999"
          	name="Length Attribute"
          	class="org.jpos.iso.IFB_NUMERIC"/>
      <isofield
		id="1"
		length="999"
		name="Table Length"
		pad="true"
		class="org.jpos.iso.IFB_NUMERIC"/>
	...........
      <isofield
		id="1"
		length="999"
		name="Amount"
		pad="true"
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alejandro Revilla | 4 Jun 2005 15:15
Favicon
Gravatar

Re: Question on Release 1.4.4

>
> I am still trying to figure out how to include more than one table, in one
> field. I bought the JPOS programmers guide, got a some information on how to
> create custom packager. Which I can use to create first Table, but could not
> find out how I can add more Tables.
> 
> Below snippet shows the first Table(14) fields (Length Attribute, ...,
> Amount). I need to add Tables 49... 
> <isofieldpackager
>       id="63"
>       length="999"
>       name="Tables 10-60"
>       class="org.jpos.iso.IF_CHAR" 
>
the 'envelope' field packager has to be a binary one, You
should use IFB_LLBINARY instead of IF_CHAR there.

>
>       packager="org.jpos.iso.packager.CustomTable14FieldPackager">
>       <isofield
>           	id="0"
>           	length="999"
>           	name="Length Attribute"
>           	class="org.jpos.iso.IFB_NUMERIC"/>
>
the above length attribute is probably handled by the outter
packager, so I guess you don't need it there.

>       <isofield
> 		id="1"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sanjay Belagodu | 4 Jun 2005 22:54

RE: Question on Release 1.4.4

Alejandro,
Let me clarify some of the terms I used in my mail.
Table : Is a set fields and values, just like a Auth message.

According to the specification the Auth Message we have to send, Bit 63
(id=63) will have a set of Tables.Each of these Tables have some minimum set
of fields like the TableId, TableLength and other information. 

				Bit 63, Table 14
____________________________________________________________________________
___________________________
Length of Bit 63	| Length of Table 14	|	Table ID	|
ACI	|	Tran ID			|
	74 		|	48			|	1 4
|	59 	|	b (fifteen spaces) b	|
____________________________________________________________________________
___________________________

				Bit 63, Table 14 (Cont.)
____________________________________________________________________________
_________________________________
Validation Code	|	MSDI 	|	RPSI	|	First Authorized
Amount 	|	Total Authorized Amount	|
b b b b 		|	b 	|	7 	|	0 (12 zeros)
0 			|	0 (12 zeros) 0		| 
____________________________________________________________________________
_________________________________

				Bit 63 - Table 33 
____________________________________________________________________________
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Salter | 4 Jun 2005 23:10

Re: Question on Release 1.4.4

Sanjay Belagodu wrote:

> 
> 				Bit 63, Table 14 (Cont.)
> ____________________________________________________________________________
> _________________________________
> Validation Code	|	MSDI 	|	RPSI	|	First Authorized
> Amount 	|	Total Authorized Amount	|
> b b b b 		|	b 	|	7 	|	0 (12 zeros)
> 0 			|	0 (12 zeros) 0		| 
> ____________________________________________________________________________
> _________________________________

I think there is a typo there, should that read MSDI?

If so this is a weird EDC format with variable and fixed length fields 
with terminators?

Do you know the company ISD or FDC at all?  I supplied them (ISD) with a 
set of JPos sources to deal with the message format.  I didn't bother 
splitting these 'tables' down, but wrapped them asis in a terminated 
field.  I also didn't add to the repository, I am waiting for them to be 
used (and tested) in a real environment, I only worked from a partial 
message layout.

-- Mark
Permalink | Reply | 0 comments |
headers
Sanjay Belagodu | 4 Jun 2005 23:26

RE: Question on Release 1.4.4

I think there is a typo there, should that read MSDI?
> Mark, This is MSDI = Market Specific Data Indicator

If so this is a weird EDC format with variable and fixed length fields 
with terminators?
> If you are referring to the "|" as terminators, I added those to show the
specification in a table format. Sorry if it confused you.

Do you know the company ISD or FDC at all?  I supplied them (ISD) with a 
set of JPos sources to deal with the message format.  I didn't bother 
splitting these 'tables' down, but wrapped them asis in a terminated 
field.  I also didn't add to the repository, I am waiting for them to be 
used (and tested) in a real environment, I only worked from a partial 
message layout.
> No, I do not know these companies. I defiantly do not mind looking at
those sources and finding out if it can help us (if it is possible to get
hold of them)

thanks
sanjay

 
Yahoo! Groups Links
Permalink | Reply | 1 comment |

Gmane