community-content

Forum Replies Created

Viewing 15 posts - 196 through 210 (of 9,652 total)
  • Author
    Posts
  • in reply to: Which is the best Tool BizTalk vs iWay #26344

    Hi,

    I would like to share this link here because it gave a good idea which areas need to address when choosing a product from the multiple similar products

    http://www.infoq.com/…/ESB-Integration

    in reply to: Which is the best Tool BizTalk vs iWay #26343

    Thanks NISHIl

    in reply to: Which is the best Tool BizTalk vs iWay #26342

    Iway has built up their own integration tool

    http://www.informationbuilders.com/…/realtime

    You will find many 3rd Party integration tools.

    Its always best to go with standard Integration products like BizTalk/Oracle fusion/IBM Websphere been used worldwide because of the support they provide and also because of resource availability in the market who know these products best and are productive from day one.

    in reply to: Which is the best Tool BizTalk vs iWay #26341

    I understand that BizTalk+iWay adapter suit is required  to achieve some business scenarios?. But i read using iWay you can do integration like BizTalk.

    so, in real time how to differentiate in terms of integration.

    in reply to: Which is the best Tool BizTalk vs iWay #26340

    Iway says they can connect Microsoft BizTalk Server to over 300 Enterprise Information Systems.

    http://www.informationbuilders.com/biztalk

    It depends upon your Integration scenario and if the current adapters shipped with BizTalk Server can work out or not.

    Ideal answer will be option 1 but it always gives rise to politics with the teams blaming each other when Server gets slow and impacts development.

    Try with first option 1 and then switch to option2(Virtual Server) if they fight a lot 😉 .

    Important here is how have you designed your architecture?

    DevPC->Dev Env->PreProd->Prod or Dev->PreProd->Prod?

    I have experienced all types of scenarios so it varies from your budget and scope of the project

    At one customer we had

    Individual virtual Pc's(for development)->Dev Server(with auto continuous deployment/test rutines every 2 hours,so what you deploy should work irrespective of machine)->PreProd Environment->Prod Environment.

    in reply to: Which is the best Tool BizTalk vs iWay #26338

    Can you share some docs and links related to iWay and give idea about iWay where it is best fit in real time.

    in reply to: Which is the best Tool BizTalk vs iWay #26337

    BizTalk is an Integration platform and Iway normally has been providing 3rd party BizTalk adapters for years for scenarios where standard adapters are not available or are not capable of achieving the expected results.

    in reply to: Receive binary file correlated on RecievedFileName #26334

    I was unable to promote the property by using correlation in Orchestration . i tried your solution but didn't work alone however also calling Context.Promote for the ReceivedFileName property did the trick! Feels like over doing it by having to resort to custom pipeline though. Thanks for the point in the right direction! 🙂

    Regards Robert

    in reply to: how to change encoding in Schema for Special Character? #26333

    While Creating Message in Biztalk set TargetCharset to "ISO-8859-1"

    Message(XMLNorm.TargetCharset) = "ISO-8859-1"

    in reply to: Maps :Multiple record to single record #26332

    Did you try direct 1:1 field mapping without looping functoid?

    So dont map anything to Record node on the destination side…direct field to field mapping.

    If you need only 1 record on the destination side to contain all the fields then you dont need a looping functoid.

    I think it should work fine.

    in reply to: Passing dummy inputs to one record in Maps #26331

    Need to look at the project as how have you implemented the mapping for first 2 scenarios.

    Have you created 3 different maps for 3 scenarios or a single map to handle all scenarios?

    How it is decided if its scenario 1 or 2 or 3 from the input XML?

    in reply to: Passing dummy inputs to one record in Maps #26330

    Output XML:

    productRequest> <sender>SAPGT</sender> <receiver>MDI</receiver> <messageId>1000000233_0000000000433844-d19f25</messageId>

    -<product> <action>U</action> <partId>1000000233</partId> <partDescription>CRO SRV GASKET NICKEL</partDescription> <unit/> <netWeight/> <grossWeight/> <scheduleB/> <notes/> <pcoo1/> <eccnum/> <htsId/> <siteId/> <flexCharacterAttr1/> <flexCharacterAttr2/> <flexCharacterAttr3/> <flexCharacterAttr4/> <flexCharacterAttr5/> <flexCharacterAttr9/> <sourceSystem/> <docDisplay/> <exportValidation/> <importValidation/> -<productCountry> <action>U</action> <countryCode>CL</countryCode> <partDescription>CRO SRV GASKET NICKEL</partDescription> <countryOfOrigin>IN</countryOfOrigin> <notes/> <unitOfMeasure1>EA</unitOfMeasure1> <flexCharacterAttr1>HALB</flexCharacterAttr1> <flexCharacterAttr2>EA</flexCharacterAttr2> <flexCharacterAttr3>1000000233</flexCharacterAttr3> <flexCharacterAttr4/> <flexCharacterAttr5>BFVRAWRAWRAW</flexCharacterAttr5> <flexCharacterAttr9>1000000233</flexCharacterAttr9> <sourceSystem>SAPED1</sourceSystem> <eccnum/> <hts>85030090</hts> </productCountry> </product> </productRequest>

    CountryCode suggests CL (means its Chile) so we need to pass dummy values to <Product>

    in reply to: Passing dummy inputs to one record in Maps #26329

    INput XML:

    -<Receive xmlns=”microsoft.lobservices.sap/…/Receive”>-<idocData>-<EDI_DC40 xmlns=”microsoft.lobservices.sap/…/702″><TABNAM xmlns=”microsoft.lobservices.sap/…/TABNAM><MANDT xmlns=”microsoft.lobservices.sap/…/MANDT><DOCNUM xmlns=”microsoft.lobservices.sap/…/DOCNUM><DOCREL xmlns=”microsoft.lobservices.sap/…/DOCREL><STATUS xmlns=”microsoft.lobservices.sap/…/STATUS><DIRECT xmlns=”microsoft.lobservices.sap/…/DIRECT><OUTMOD xmlns=”microsoft.lobservices.sap/…/OUTMOD><EXPRSS xmlns=”microsoft.lobservices.sap/…/><TEST xmlns=”microsoft.lobservices.sap/…/><IDOCTYP xmlns=”microsoft.lobservices.sap/…/IDOCTYP><CIMTYP xmlns=”microsoft.lobservices.sap/…/CIMTYP><MESTYP xmlns=”microsoft.lobservices.sap/…/MESTYP><MESCOD xmlns=”microsoft.lobservices.sap/…/><MESFCT xmlns=”microsoft.lobservices.sap/…/><STD xmlns=”microsoft.lobservices.sap/…/><STDVRS xmlns=”microsoft.lobservices.sap/…/><STDMES xmlns=”microsoft.lobservices.sap/…/><SNDPOR xmlns=”microsoft.lobservices.sap/…/SNDPOR><SNDPRT xmlns=”microsoft.lobservices.sap/…/SNDPRT><SNDPFC xmlns=”microsoft.lobservices.sap/…/><SNDPRN xmlns=”microsoft.lobservices.sap/…/SNDPRN><SNDSAD xmlns=”microsoft.lobservices.sap/…/><SNDLAD xmlns=”microsoft.lobservices.sap/…/><RCVPOR xmlns=”microsoft.lobservices.sap/…/RCVPOR><RCVPRT xmlns=”microsoft.lobservices.sap/…/RCVPRT><RCVPFC xmlns=”microsoft.lobservices.sap/…/><RCVPRN xmlns=”microsoft.lobservices.sap/…/RCVPRN><RCVSAD xmlns=”microsoft.lobservices.sap/…/><RCVLAD xmlns=”microsoft.lobservices.sap/…/><CREDAT xmlns=”microsoft.lobservices.sap/…/CREDAT><CRETIM xmlns=”microsoft.lobservices.sap/…/CRETIM><REFINT xmlns=”microsoft.lobservices.sap/…/><REFGRP xmlns=”microsoft.lobservices.sap/…/><REFMES xmlns=”microsoft.lobservices.sap/…/><ARCKEY xmlns=”microsoft.lobservices.sap/…/><SERIAL xmlns=”microsoft.lobservices.sap/…/EDI_DC40>-<E2MARAM007GRP xmlns=”microsoft.lobservices.sap/…/><MAKTX>CRO SRV GASKET NICKEL</MAKTX><SPRAS_ISO/><SEGMENTPAD/></E2MAKTM001>-<E2MAKTM001><DATAHEADERCOLUMN_SEGNAM>E2MAKTM001</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000007</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000001</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>03</DATAHEADERCOLUMN_HLEVEL><MSGFN/><SPRAS/><MAKTX>1X2 & 1.5X2 25-275 PSIG SOFT GOODS</MAKTX><SPRAS_ISO/><SEGMENTPAD/></E2MAKTM001>-<E2MARCM005GRP>-<E2MARCM005><DATAHEADERCOLUMN_SEGNAM>E2MARCM005</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000008</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000001</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>03</DATAHEADERCOLUMN_HLEVEL><MSGFN/><WERKS>1201</WERKS><PSTAT/><LVORM/><BWTTY/><MAABC/><KZKRI/><EKGRP/><AUSME/><DISPR/><DISMM/><DISPO/><PLIFZ/><WEBAZ/><PERKZ/><AUSSS/><DISLS/><BESKZ/><SOBSL/><MINBE/><EISBE/><BSTMI/><BSTMA/><BSTFE/><BSTRF/><MABST/><LOSFX/><SBDKZ/><LAGPR/><ALTSL/><KZAUS/><AUSDT/><NFMAT/><KZBED/><MISKZ/><FHORI/><PFREI/><FFREI/><RGEKZ/><FEVOR/><BEARZ/><RUEZT/><TRANZ/><BASMG/><DZEIT/><MAXLZ/><LZEIH/><KZPRO/><GPMKZ/><UEETO/><UEETK/><UNETO/><WZEIT/><ATPKZ/><VZUSL/><HERBL/><INSMK/><SSQSS/><KZDKZ/><UMLMC/><LADGR/><XCHPF/><USEQU/><LGRAD/><AUFTL/><PLVAR/><OTYPE/><OBJID/><MTVFP/><PERIV/><KZKFK/><VRVEZ/><VBAMG/><VBEAZ/><LIZYK/><BWSCL/><KAUTB/><KORDB/><STAWN>8503.0090</STAWN><HERKL>IN</HERKL><HERKR>CL</HERKR><EXPME/><MTVER/><PRCTR/><TRAME/><MRPPP/><SAUFT/><FXHOR/><VRMOD/><VINT1/><VINT2/><STLAL/><STLAN/><PLNNR/><APLAL/><LOSGR/><SOBSK/><FRTME/><LGPRO/><DISGR/><KAUSF/><QZGTP/><TAKZT/><RWPRO/><COPAM/><ABCIN/><AWSLS/><SERNP/><STDPD/><SFEPR/><XMCNG/><QSSYS/><LFRHY/><RDPRF/><VRBMT/><VRBWK/><VRBDT/><VRBFK/><AUTRU/><PREFE/><PRENC/><PRENO/><PREND/><PRENE/><PRENG/><ITARK/><PRFRQ/><KZKUP/><STRGR/><LGFSB/><SCHGT/><CCFIX/><EPRIO/><QMATA/><PLNTY/><MMSTA/><SFCPF/><SHFLG/><SHZET/><MDACH/><KZECH/><MMSTD/><MFRGR/><FVIDK/><INDUS/><MOWNR/><MOGRU/><CASNR/><GPNUM/><STEUC/><FABKZ/><MATGR/><LOGGR/><VSPVB/><DPLFS/><DPLPU/><DPLHO/><MINLS/><MAXLS/><FIXLS/><LTINC/><COMPL/><CONVT/><FPRFM/><SHPRO/><FXPRU/><KZPSP/><OCMPF/><APOKZ/><AHDIS/><EISLO/><NCOST/><MEGRU/><ROTATION_DATE/><UCHKZ/><UCMAT/><IUID_RELEVANT/><IUID_TYPE/><UID_IEA/><SEGMENTPAD/></E2MARCM005>-<E2MARDM001><DATAHEADERCOLUMN_SEGNAM>E2MARDM001</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000009</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000008</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>04</DATAHEADERCOLUMN_HLEVEL><MSGFN>005</MSGFN><LGORT>0100</LGORT><PSTAT>DL</PSTAT><LVORM>/</LVORM><DISKZ>/</DISKZ><LSOBS>/</LSOBS><LMINB>/</LMINB><LBSTF>/</LBSTF><HERKL/><EXPPG>/</EXPPG><EXVER>/</EXVER><LGPBE>/</LGPBE><PRCTL>/</PRCTL><LWMKB>/</LWMKB><BSKRF>/</BSKRF><SEGMENTPAD/></E2MARDM001></E2MARCM005GRP>-<E2MVKEM002><DATAHEADERCOLUMN_SEGNAM>E2MVKEM002</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000010</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000001</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>03</DATAHEADERCOLUMN_HLEVEL><MSGFN/><VKORG/><VTWEG/><LVORM/><VERSG/><BONUS/><PROVG/><SKTOF/><VMSTA/><VMSTD/><AUMNG/><LFMNG/><EFMNG/><SCMNG/><SCHME/><VRKME/><MTPOS/><DWERK>1201</DWERK><PRODH/><PMATN/><KONDM/><KTGRM/><MVGR1/><MVGR2/><MVGR3/><MVGR4/><MVGR5/><SSTUF/><PFLKS/><LSTFL/><LSTVZ/><LSTAK/><PRAT1/><PRAT2/><PRAT3/><PRAT4/><PRAT5/><PRAT6/><PRAT7/><PRAT8/><PRAT9/><PRATA/><VAVME/><RDPRF/><MEGRU/><PMATN_EXTERNAL/><PMATN_VERSION/><PMATN_GUID/><SEGMENTPAD/></E2MVKEM002>-<E2MVKEM002><DATAHEADERCOLUMN_SEGNAM>E2MVKEM002</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000011</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000001</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>03</DATAHEADERCOLUMN_HLEVEL><MSGFN/><VKORG/><VTWEG/><LVORM/><VERSG/><BONUS/><PROVG/><SKTOF/><VMSTA/><VMSTD/><AUMNG/><LFMNG/><EFMNG/><SCMNG/><SCHME/><VRKME/><MTPOS/><DWERK/><PRODH/><PMATN/><KONDM/><KTGRM/><MVGR1/><MVGR2/><MVGR3/><MVGR4/><MVGR5/><SSTUF/><PFLKS/><LSTFL/><LSTVZ/><LSTAK/><PRAT1/><PRAT2/><PRAT3/><PRAT4/><PRAT5/><PRAT6/><PRAT7/><PRAT8/><PRAT9/><PRATA/><VAVME/><RDPRF/><MEGRU/><PMATN_EXTERNAL/><PMATN_VERSION/><PMATN_GUID/><SEGMENTPAD/></E2MVKEM002>-<E2MVKEM002><DATAHEADERCOLUMN_SEGNAM>E2MVKEM002</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000012</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000001</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>03</DATAHEADERCOLUMN_HLEVEL><MSGFN/><VKORG/><VTWEG/><LVORM/><VERSG/><BONUS/><PROVG/><SKTOF/><VMSTA/><VMSTD/><AUMNG/><LFMNG/><EFMNG/><SCMNG/><SCHME/><VRKME/><MTPOS/><DWERK/><PRODH/><PMATN/><KONDM/><KTGRM/><MVGR1/><MVGR2/><MVGR3/><MVGR4/><MVGR5/><SSTUF/><PFLKS/><LSTFL/><LSTVZ/><LSTAK/><PRAT1/><PRAT2/><PRAT3/><PRAT4/><PRAT5/><PRAT6/><PRAT7/><PRAT8/><PRAT9/><PRATA/><VAVME/><RDPRF/><MEGRU/><PMATN_EXTERNAL/><PMATN_VERSION/><PMATN_GUID/><SEGMENTPAD/></E2MVKEM002>-<E2MVKEM002><DATAHEADERCOLUMN_SEGNAM>E2MVKEM002</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000013</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000001</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>03</DATAHEADERCOLUMN_HLEVEL><MSGFN/><VKORG/><VTWEG/><LVORM/><VERSG/><BONUS/><PROVG/><SKTOF/><VMSTA/><VMSTD/><AUMNG/><LFMNG/><EFMNG/><SCMNG/><SCHME/><VRKME/><MTPOS/><DWERK/><PRODH/><PMATN/><KONDM/><KTGRM/><MVGR1/><MVGR2/><MVGR3/><MVGR4/><MVGR5/><SSTUF/><PFLKS/><LSTFL/><LSTVZ/><LSTAK/><PRAT1/><PRAT2/><PRAT3/><PRAT4/><PRAT5/><PRAT6/><PRAT7/><PRAT8/><PRAT9/><PRATA/><VAVME/><RDPRF/><MEGRU/><PMATN_EXTERNAL/><PMATN_VERSION/><PMATN_GUID/><SEGMENTPAD/></E2MVKEM002>-<E2MVKEM002><DATAHEADERCOLUMN_SEGNAM>E2MVKEM002</DATAHEADERCOLUMN_SEGNAM><DATAHEADERCOLUMN_MANDT>120</DATAHEADERCOLUMN_MANDT><DATAHEADERCOLUMN_DOCNUM>0000000000433844</DATAHEADERCOLUMN_DOCNUM><DATAHEADERCOLUMN_SEGNUM>000014</DATAHEADERCOLUMN_SEGNUM><DATAHEADERCOLUMN_PSGNUM>000001</DATAHEADERCOLUMN_PSGNUM><DATAHEADERCOLUMN_HLEVEL>03</DATAHEADERCOLUMN_HLEVEL><MSGFN/><VKORG/><VTWEG/><LVORM/><VERSG/><BONUS/><PROVG/><SKTOF/><VMSTA/><VMSTD/><AUMNG/><LFMNG/><EFMNG/><SCMNG/><SCHME/><VRKME/><MTPOS/><DWERK/><PRODH/><PMATN/><KONDM/><KTGRM/><MVGR1/><MVGR2/><MVGR3/><MVGR4/><MVGR5/><SSTUF/><PFLKS/><LSTFL/><LSTVZ/><LSTAK/><PRAT1/><PRAT2/><PRAT3/><PRAT4/><PRAT5/><PRAT6/><PRAT7/><PRAT8/><PRAT9/><PRATA/><VAVME/><RDPRF/><MEGRU/><PMATN_EXTERNAL/><PMATN_VERSION/><PMATN_GUID/><SEGMENTPAD/></E2MVKEM002></E2MARAM007GRP></idocData></Receive>

    in reply to: Receive binary file correlated on RecievedFileName #26327

    You can fix this in the custom Receive pipeline by removing the extra path so both ReceivedFileName context properties will have same value.

Viewing 15 posts - 196 through 210 (of 9,652 total)