9 Replies Latest reply: Jul 1, 2012 11:31 PM by Anuj Dwivedi--Oracle RSS

    Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne

    CD2006
      Hi,

      For Inbound SFTP transfer is there a way to avoid using standard B2B file-naming convention at source files?

      We tried the following for B2B host external delivery channel (SFTP) which would pick up the files from trading partner directory -

      1. Set oracle.tip.adapter.b2b.allTPInOneDirectory = false
      2. Create a directory specific to the trading partner and have the Trading Partner drop the files in the Trading Partner specific folder.

      However, it did not work; the transfer was successful only when standard file name format was specified and used for files.

      We are using 'Oracle B2B 10.1.2 MLR16' version - is this feature not available in this version?

      Sincerely,
      CD
        • 1. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
          Anuj Dwivedi--Oracle
          You need to set oracle.tip.adapter.b2b.allTPInOneDirectory=True to indicate B2B to identify Trading Partners based on the name of the Directory. Please refer -

          http://www.b2bgurus.com/2007/09/oracle-as-b2b-various-features-in-ftp.html

          Regards,
          Anuj
          • 2. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
            CD2006
            Thanks Anuj!

            From the above link -

            a. For External Delivery Channel.

            i. Identification of Trading Partner is based on the name of the file and the name should follow the patterns as nameOfTP_UniqueID.

            ii.Identification of Trading Partneris based on the name of the Directory. To enable this it is required to set
            oracle.tip.adapter.b2b.allTPInOneDirectory= True as part of tip.properties setting.

            Is either i or ii sufficient or both i & ii are required for the SFTP/FTP transfer?

            I tried ii with leaving '*filename format*' field blank for the host external delivery channel however, it gave following exception - Error -: AIP-50083: Document protocol identification error

            Are there any restrictions regarding directory name (and URL-hierarchy) for ii to work?
            • 3. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
              Anuj Dwivedi--Oracle
              Is either i or ii sufficient or both i & ii are required for the SFTP/FTP transfer?
              Yes, either of them is sufficient for Oracle B2B to identify the partners.
              Are there any restrictions regarding directory name (and URL-hierarchy) for ii to work?
              The directory name must be same as partner name. For example, if the remote TP name is GlobalServices, then directory may be like -

              /etc/abc/GlobalServices

              Regards,
              Anuj
              • 4. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
                CD2006
                Thanks Anuj

                It throws the following error now -

                Description: Unable to identify the document protocol of the message
                StackTrace:
                Error -: AIP-50083: Document protocol identification error
                     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3354)
                     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1725)
                     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2657)
                     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2527)
                     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2482)
                     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:530)
                     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:376)
                     at java.lang.Thread.run(Thread.java:534)

                These are the details for the Inbound transfer -

                preserve filename=true

                filename=SampleFile.txt

                filename format (specified in host external delivery channel) =%FROM_PARTY%_%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%

                fullpath=/../SystemB/SampleFile.txt SystemB is the remote trading partner (FROM_PARTY); it has generic identifier created with same name.

                The transfer works if the filename is in this format: %FROM_PARTY%_%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%. Do any of the other parameters for delivery channel such as directory name format, Directory name format separator need to be used/updated?

                Thanks,
                CD
                • 5. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
                  Anuj Dwivedi--Oracle
                  Description: Unable to identify the document protocol of the message
                  If the inbound file is a XML file then provide the identification XPath and value (optional) in Document definition. Oracle B2B will identify the incoming document on the basis of this XPath. If incoming document is a flat file then provide the start position, end position and value in Document Definition for identification of the document.

                  Above changes will need agreements to be redeployed.

                  Regards,
                  Anuj

                  Edited by: Anuj Dwivedi on Jun 13, 2012 3:09 PM
                  • 6. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
                    CD2006
                    Anuj,

                    These are the protocol - document definition details:

                    Business Protocol          Custom Document over Generic Exchange
                    Document Protocol          Custom

                    Start position of Identification for non-XML Document: 1
                    End position of Identification for non-XML Document: 3
                    Identification Value: ABC

                    It gave this error -
                    Description: B2B adapter general error
                    StackTrace:
                    Error -: AIP-50031: B2B adapter general error



                    Also, option 1. Identification of Trading Partner is based on the name of the file and the name should follow the patterns as nameOfTP_UniqueID did not work.

                    Filename: SYSTEMB_20120613101010
                    Pickup directory: ../../SYSTEMB
                    Filename format left blank.
                    Description: Unable to identify the document protocol of the message
                    StackTrace:
                    Error -: AIP-50083: Document protocol identification error


                    thanks,
                    CD
                    • 7. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
                      Anuj Dwivedi--Oracle
                      Start position of Identification for non-XML Document: 1
                      End position of Identification for non-XML Document: 3
                      Identification Value: ABC
                      Can you post the initial content of your message here?
                      Description: B2B adapter general error
                      As the name indicates, this error is general and does not really give information that where is the issue. can you post the log in debug mode here or mail it to my id (in my profile)?
                      Also, option 1. Identification of Trading Partner is based on the name of the file and the name should follow the patterns as nameOfTP_UniqueID did not work.
                      Description: Unable to identify the document protocol of the message
                      Same reason. The incoming data does not matches with any identification xpath (if it is XML) or with any combination of start position, end position and value (for flat files) defined in all the deployed document definitions. Make sure that you have defined identification xpath or start position, end position and value (for flat files) in the deployed document definition and it matches with incoming payload.

                      Regards,
                      Anuj
                      • 8. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
                        CD2006
                        Hi Anuj,

                        We are planning to upgrade to B2B 11g and were able to confirm that the restriction on file name format can be avoided.

                        Is there a way to import existing B2B config, or a specific agreement from 10g to 11g? It looks like 11g needs metadata zip file and and can not use xml agreement or config file exported from 10g.

                        Thanks,
                        • 9. Re: Filename Format in FTP Delivery Channel - oracle.tip.adapter.b2b.allTPInOne
                          Anuj Dwivedi--Oracle
                          You may export 10g configuration as 11g metadata. Please refer -

                          https://blogs.oracle.com/oracleb2bgurus/entry/export_the_metadata_from_10g_t

                          Regards,
                          Anuj