OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: Test Indicator Issue


Bob, see response inline:

>
> The tables which select the URL to which to deliver the payloads, whether
> these tables be in the application code on in some middleware,
> would have to
> differ between the production system and the test system.  And there might
> be dozens of URL's each of which needs both a production and a development
> entry.  And the tables might be stored in the same database as
> other tables,
> so when a database is copied from production to test, the changes
> have to be
> re-introduced.
>

If I understand your point correctly you're saying that by having a test
flag you're able to maintain the same data in both a test and production
database and can easily copy data between the two, correct?

If so, then I think one could say the same thing when two separate URL's are
used, for example:

http://test.company.com/ebxmlhandler

and

http://production.company.com/ebxmlhandler

Both URL's could share a single trading partner database instance, but use
separate processing logic on the application payload.


Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@8760.com
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions

> -----Original Message-----
> From: Miller, Robert (GXS) [mailto:Robert.Miller@gxs.ge.com]
> Sent: Monday, November 27, 2000 10:08 AM
> To: ebxml-transport@lists.ebxml.org
> Subject: RE: Test Indicator Issue
>
>
> List-Unsubscribe:
>  <mailto:ebxml-transport-request@lists.ebxml.org?body=unsubscribe>
> List-Archive: <http://lists.ebxml.org/archives/ebxml-transport>
> List-Help: <http://lists.ebxml.org/doc/email-manage.html>,
>  <mailto:ebxml-transport-request@lists.ebxml.org?body=help>
>
> Dick,
>
> The tables which select the URL to which to deliver the payloads, whether
> these tables be in the application code on in some middleware,
> would have to
> differ between the production system and the test system.  And there might
> be dozens of URL's each of which needs both a production and a development
> entry.  And the tables might be stored in the same database as
> other tables,
> so when a database is copied from prodcution to test, the changes
> have to be
> re-introduced.
>
> Cheers,
>         Bob
>
> -----Original Message-----
> From: Dick Brooks [mailto:dick@8760.com]
> Sent: Monday, November 27, 2000 9:56 AM
> To: Miller, Robert (GXS); Nikola Stojanovic;
> ebxml-transport@lists.ebxml.org
> Subject: RE: Test Indicator Issue
>
>
> Bob,
>
> I don't understand how separate test/production URL's does the following:
>
> > referenced below.  But I contend that these other ways reduce the
> > parallelism of the test system to a greater extent than does a
> test flag.
>
> Please explain. Thanks.
>
>
> Dick Brooks
> Group 8760
> 110 12th Street North
> Birmingham, AL 35203
> dick@8760.com
> 205-250-8053
> Fax: 205-250-8057
> http://www.8760.com/
>
> InsideAgent - Empowering e-commerce solutions
>
> > -----Original Message-----
> > From: Miller, Robert (GXS) [mailto:Robert.Miller@gxs.ge.com]
> > Sent: Monday, November 27, 2000 9:23 AM
> > To: Nikola Stojanovic; ebxml-transport@lists.ebxml.org
> > Subject: RE: Test Indicator Issue
> >
> >
> > List-Unsubscribe:
> >  <mailto:ebxml-transport-request@lists.ebxml.org?body=unsubscribe>
> > List-Archive: <http://lists.ebxml.org/archives/ebxml-transport>
> > List-Help: <http://lists.ebxml.org/doc/email-manage.html>,
> >  <mailto:ebxml-transport-request@lists.ebxml.org?body=help>
> >
> > Yes there are other ways to indicate a 'test' message, two of which are
> > referenced below.  But I contend that these other ways reduce the
> > parallelism of the test system to a greater extent than does a
> test flag.
> > Use of a test flag is a proven practice. So my advice is add the
> > test flag -
> > "If it ain't broke, don't fix it!"
> >
> > Cheers,
> >        Bob Miller
> >
> > -----Original Message-----
> > From: Nikola Stojanovic [mailto:nhomest1@twcny.rr.com]
> > Sent: Monday, November 27, 2000 8:57 AM
> > To: ebxml-transport@lists.ebxml.org
> > Subject: Re: First issue [was: Outstanding Issues - LONG please red to
> > end}
> >
> >
> > <Dick Brooks>
> > There are others means to indicate a "test" versus "production" message
> > exchange. For example:
> > - separate production and test ebxml handler URL's (mailboxes,
> FTP sites,
> > etc.)
> > - separate production and test Party ID's
> > </Dick Brooks>
> >
> > Makes sense. I agree.
> >
> > Nikola
> >



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC