You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Mike <mz...@gmail.com> on 2012/06/04 10:15:53 UTC
Re: Fedex Shipment Gateway Configuration is not available
Reviving Thread:
Jacques, can you tell me the status of Fedex integration today? Does it
still not work?
Thanks
On Sat, Feb 26, 2011 at 1:08 AM, Jacques Le Roux <
jacques.le.roux@les7arts.com> wrote:
> The Fedex "API" has changed, here is an analysis I did for a client in
> August
>
> <<OFBiz
>
> OFBiz is using the "old" way: the "Ship Manager Direct XML API"
> (introduced in August 2007).
> Currently in OFBiz there are entities for shipment carriers
> (ShipmentTypeData.xml) but they are not yet used
> https://cwiki.apache.org/**confluence/display/OFBIZ/**
> Third+Party+Payment+and+**Shipment+Configuration#**
> ThirdPartyPaymentandShipmentCo**nfiguration-**ShipmentConfiguration<https://cwiki.apache.org/confluence/display/OFBIZ/Third+Party+Payment+and+Shipment+Configuration#ThirdPartyPaymentandShipmentConfiguration-ShipmentConfiguration>
> Though some are set in DemoShipping.xml
> There is also a ShipmentTypeData.xml file but I did not dig in.
> I'd have to check it closely but it looks like OOTB OFBiz handles only one
> item by order so far.
>
> Fedex
>
> Fedex has deprecated the API used by OFBiz and recommend now to use rather
> "FedEx Web Services":
> http://fedex.com/us/developer/**product/migration.html<http://fedex.com/us/developer/product/migration.html>
> Abstract: <<Since FedEx Web Services was introduced in August 2007, the
> FedEx Ship Manager® API and FedEx Ship Manager® Direct
> solutions were placed in containment and no new services or features have
> been added. On May 31, 2012, FedEx will retire our legacy
> FedEx Ship Manager API and FedEx Ship Manager Direct backend systems.
> Customers that have not transitioned to FedEx Web Services or
> another FedEx electronic shipping solution by this date will not be able
> to submit FedEx Ship Manager API or FedEx Ship Manager
> Direct transactions through the FedEx systems.>>
> FAQ: http://images.fedex.com/us/**developer/downloads/**migrationFAQ.pdf<http://images.fedex.com/us/developer/downloads/migrationFAQ.pdf>
>
> Axis: "FedEx Web Services" were tested with jdk 1.5 and are using Axis
> 1.4. In OFBiz Axis 1.4 has been replaced by Axis 2 some
> months ago. I can't still see the Axis 1.4 jar though and I'm not quite
> sure yet if it's still usable. Anyway does not sound like a
> big deal since "FedEx Web Services" needs more than Axis 1.4 jar files and
> some are not in OFBiz.
> There are both SOAP and non SOAP (using HTTP POST) services, WSDL is used
> in both cases but they don't use the same Error Handling.
> There are
> * Standard services for general use and do not require certification.
> * Advanced services for proprietary developers and will require
> certification prior to production launch.
> Both Web services levels offer sample code in Java, C#, C++, VB.Net and
> PHP programming languages.
> I don't think we need certification except if we want to offer Fedex
> sercices as a 3rd party and be a "FedEx compatible solution
> provider"
> http://www.fedex.com/us/**developer/product/**requirements.html<http://www.fedex.com/us/developer/product/requirements.html>
>
> Fedex provides 4 types of web services
> * Web Services for Shipping: Shipment/Label/Express Tag (create, cancel,
> validate), Rate, Package Movement, Tracking and Visibility,
> Address validation, Courier Dispatch Service, Return (print label from AMI
> site), ...
> * Web Services for Office and Print: enable users to manage the creation,
> configuration and submission of FedEx Office digital print
> order
> * Ship Manager Server: a solution for high-volume shippers who need to
> process, label, and ship large volumes of packages. It allows
> full integration of the FedEx service modules - tracking, rating and
> routing - with a company's existing computer systems.
> * Plug-ins: for customers that need quick Web based solutions with minimal
> IT/Developer Resources (there are also related
> Integration Tools: Web Integration Wizard and QuickShip modules)
>
> At 1st glance it looks like we need at least FedEx "Web Services for
> Shipping", Integration Tools do not seem to qualify. But when I
> digged a bit deeper I found that only "Ship Manager Server" has service
> guarantee for high volume and network reliability
> <<The decision to use FedEx Web Services is an easy one
> We recommend FedEx Web Services as your integration solution if your
> business has:
> * Online transactions that need immediate response.
> * Low to medium transaction volume.
> If your business has a high transaction volume, we recommend FedEx Ship
> Manager® Server.>>
> http://www.fedex.com/us/**developer/product/solutions.**html<http://www.fedex.com/us/developer/product/solutions.html>
> So eventually it looks like "Ship Manager Server" is more appropriate, but
> this is not my decision of course.
>
> These links are useful for an overview:
> http://www.fedex.com/us/**services/ataglance.html<http://www.fedex.com/us/services/ataglance.html>
> http://fedex.com/us/solutions/**overview.html<http://fedex.com/us/solutions/overview.html>
> Interactive guide: http://fedex.com/us/helpguide/**index.html<http://fedex.com/us/helpguide/index.html>
> This last one is rather long but looks like user references
> (functionalities) and more usable for Fedex beginners (devs included):
> http://images.fedex.com/us/**services/pdf/Service_Guide_**2010.pdf<http://images.fedex.com/us/services/pdf/Service_Guide_2010.pdf>
>
> Finally, I must say it's not easy to find your way there, but OFBiz is the
> same when you begin...
>
> I will see now what the community thinks about it. If OK on both side I'd
> like to introduce the "FedEx Web Services" in OFBiz...>>
>
> HTH, feel free to contribute...
>
> Jacques
>
> From: "masionas" <mi...@gmail.com>
>
> Hi Guys,
>>
>> Is Fedex integration working in the recent trunk? It used to work back in
>> old times where the config was in the shipment.properties file. Now I am
>> trying to enter config settings from Shipment Gateway Config UI under
>> facility. Put Fedex account number and meter number. Then went to outgoing
>> shipment to route segment, but it gives me error 'Fedex Shipment Gateway
>> Configuration is not available'.
>>
>> Does anyone experience same problems?
>>
>> --
>> View this message in context:
>> http://ofbiz.135035.n4.nabble.**com/Fedex-Shipment-Gateway-**
>> Configuration-is-not-**available-tp3325318p3325318.**html<http://ofbiz.135035.n4.nabble.com/Fedex-Shipment-Gateway-Configuration-is-not-available-tp3325318p3325318.html>
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>>
>
>
Re: Fedex Shipment Gateway Configuration is not available
Posted by Jacques Le Roux <ja...@les7arts.com>.
Sorry I can't accurately answer to this question. It really depends on the requirements
Jacques
Mike wrote:
> Thanks Jacques . I was wondering. Is it more common to deploy OFBiz
> systems using manually entered shipping rules?
>
> On Tue, Jun 5, 2012 at 2:28 AM, Jacques Le Roux <
> jacques.le.roux@les7arts.com> wrote:
>
>> Hi Mike,
>>
>> I was supposed to work on it for a client, but finally did not implement
>> it.
>> When I do such stuff mysfelf (even for a client) I try to do it
>> contribution minded (if the client agree).
>> I don't know if the client finally did it (I did the research and a bit of
>> the pre-analysis) but they did not contribute it
>>
>> Jacques
>>
>> Mike wrote:
>>
>>> Reviving Thread:
>>>
>>> Jacques, can you tell me the status of Fedex integration today? Does it
>>> still not work?
>>>
>>> Thanks
>>>
>>>
>>> On Sat, Feb 26, 2011 at 1:08 AM, Jacques Le Roux <
>>> jacques.le.roux@les7arts.com> wrote:
>>>
>>> The Fedex "API" has changed, here is an analysis I did for a client in
>>>> August
>>>>
>>>> <<OFBiz
>>>>
>>>> OFBiz is using the "old" way: the "Ship Manager Direct XML API"
>>>> (introduced in August 2007).
>>>> Currently in OFBiz there are entities for shipment carriers
>>>> (ShipmentTypeData.xml) but they are not yet used
>>>> https://cwiki.apache.org/****confluence/display/OFBIZ/**<https://cwiki.apache.org/**confluence/display/OFBIZ/**>
>>>> Third+Party+Payment+and+****Shipment+Configuration#**
>>>> ThirdPartyPaymentandShipmentCo****nfiguration-****ShipmentConfiguration<
>>>> https://**cwiki.apache.org/confluence/**display/OFBIZ/Third+Party+**
>>>> Payment+and+Shipment+**Configuration#**ThirdPartyPaymentandShipmentCo**
>>>> nfiguration-**ShipmentConfiguration<https://cwiki.apache.org/confluence/display/OFBIZ/Third+Party+Payment+and+Shipment+Configuration#ThirdPartyPaymentandShipmentConfiguration-ShipmentConfiguration>
>>>>>
>>>>
>>>> Though some are set in DemoShipping.xml
>>>> There is also a ShipmentTypeData.xml file but I did not dig in.
>>>> I'd have to check it closely but it looks like OOTB OFBiz handles only
>>>> one
>>>> item by order so far.
>>>>
>>>> Fedex
>>>>
>>>> Fedex has deprecated the API used by OFBiz and recommend now to use
>>>> rather
>>>> "FedEx Web Services":
>>>> http://fedex.com/us/developer/****product/migration.html<http://fedex.com/us/developer/**product/migration.html>
>>>> <http:**//fedex.com/us/developer/**product/migration.html<http://fedex.com/us/developer/product/migration.html>
>>>>>
>>>>
>>>> Abstract: <<Since FedEx Web Services was introduced in August 2007, the
>>>> FedEx Ship Manager® API and FedEx Ship Manager® Direct
>>>> solutions were placed in containment and no new services or features have
>>>> been added. On May 31, 2012, FedEx will retire our legacy
>>>> FedEx Ship Manager API and FedEx Ship Manager Direct backend systems.
>>>> Customers that have not transitioned to FedEx Web Services or
>>>> another FedEx electronic shipping solution by this date will not be able
>>>> to submit FedEx Ship Manager API or FedEx Ship Manager
>>>> Direct transactions through the FedEx systems.>>
>>>> FAQ:
>>>> http://images.fedex.com/us/****developer/downloads/****migrationFAQ.pdf<http://images.fedex.com/us/**developer/downloads/**migrationFAQ.pdf>
>>>> <http://**images.fedex.com/us/developer/**downloads/migrationFAQ.pdf<http://images.fedex.com/us/developer/downloads/migrationFAQ.pdf>
>>>>>
>>>>
>>>>
>>>> Axis: "FedEx Web Services" were tested with jdk 1.5 and are using Axis
>>>> 1.4. In OFBiz Axis 1.4 has been replaced by Axis 2 some
>>>> months ago. I can't still see the Axis 1.4 jar though and I'm not quite
>>>> sure yet if it's still usable. Anyway does not sound like a
>>>> big deal since "FedEx Web Services" needs more than Axis 1.4 jar files
>>>> and
>>>> some are not in OFBiz.
>>>> There are both SOAP and non SOAP (using HTTP POST) services, WSDL is used
>>>> in both cases but they don't use the same Error Handling.
>>>> There are
>>>> * Standard services for general use and do not require certification.
>>>> * Advanced services for proprietary developers and will require
>>>> certification prior to production launch.
>>>> Both Web services levels offer sample code in Java, C#, C++, VB.Net and
>>>> PHP programming languages.
>>>> I don't think we need certification except if we want to offer Fedex
>>>> sercices as a 3rd party and be a "FedEx compatible solution
>>>> provider"
>>>> http://www.fedex.com/us/****developer/product/****requirements.html<http://www.fedex.com/us/**developer/product/**requirements.html>
>>>> <http://www.**fedex.com/us/developer/**product/requirements.html<http://www.fedex.com/us/developer/product/requirements.html>
>>>>>
>>>>
>>>>
>>>> Fedex provides 4 types of web services
>>>> * Web Services for Shipping: Shipment/Label/Express Tag (create, cancel,
>>>> validate), Rate, Package Movement, Tracking and Visibility,
>>>> Address validation, Courier Dispatch Service, Return (print label from
>>>> AMI
>>>> site), ...
>>>> * Web Services for Office and Print: enable users to manage the creation,
>>>> configuration and submission of FedEx Office digital print
>>>> order
>>>> * Ship Manager Server: a solution for high-volume shippers who need to
>>>> process, label, and ship large volumes of packages. It allows
>>>> full integration of the FedEx service modules - tracking, rating and
>>>> routing - with a company's existing computer systems.
>>>> * Plug-ins: for customers that need quick Web based solutions with
>>>> minimal
>>>> IT/Developer Resources (there are also related
>>>> Integration Tools: Web Integration Wizard and QuickShip modules)
>>>>
>>>> At 1st glance it looks like we need at least FedEx "Web Services for
>>>> Shipping", Integration Tools do not seem to qualify. But when I
>>>> digged a bit deeper I found that only "Ship Manager Server" has service
>>>> guarantee for high volume and network reliability
>>>> <<The decision to use FedEx Web Services is an easy one
>>>> We recommend FedEx Web Services as your integration solution if your
>>>> business has:
>>>> * Online transactions that need immediate response.
>>>> * Low to medium transaction volume.
>>>> If your business has a high transaction volume, we recommend FedEx Ship
>>>> Manager® Server.>>
>>>> http://www.fedex.com/us/****developer/product/solutions.****html<http://www.fedex.com/us/**developer/product/solutions.**html>
>>>> <http://www.fedex.com/us/**developer/product/solutions.**html<http://www.fedex.com/us/developer/product/solutions.html>
>>>>>
>>>>
>>>> So eventually it looks like "Ship Manager Server" is more appropriate,
>>>> but
>>>> this is not my decision of course.
>>>>
>>>> These links are useful for an overview:
>>>> http://www.fedex.com/us/****services/ataglance.html<http://www.fedex.com/us/**services/ataglance.html>
>>>> <http:/**/www.fedex.com/us/services/**ataglance.html<http://www.fedex.com/us/services/ataglance.html>
>>>>>
>>>> http://fedex.com/us/solutions/****overview.html<http://fedex.com/us/solutions/**overview.html>
>>>> <http://fedex.**com/us/solutions/overview.html<http://fedex.com/us/solutions/overview.html>
>>>> **>
>>>> Interactive guide: http://fedex.com/us/helpguide/****index.html<http://fedex.com/us/helpguide/**index.html>
>>>> <http://fedex.com/**us/helpguide/index.html<http://fedex.com/us/helpguide/index.html>
>>>>>
>>>>
>>>> This last one is rather long but looks like user references
>>>> (functionalities) and more usable for Fedex beginners (devs included):
>>>> http://images.fedex.com/us/****services/pdf/Service_Guide_****2010.pdf<http://images.fedex.com/us/**services/pdf/Service_Guide_**2010.pdf>
>>>> <http://images.fedex.**com/us/services/pdf/Service_**Guide_2010.pdf<http://images.fedex.com/us/services/pdf/Service_Guide_2010.pdf>
>>>>>
>>>>
>>>>
>>>> Finally, I must say it's not easy to find your way there, but OFBiz is
>>>> the
>>>> same when you begin...
>>>>
>>>> I will see now what the community thinks about it. If OK on both side I'd
>>>> like to introduce the "FedEx Web Services" in OFBiz...>>
>>>>
>>>> HTH, feel free to contribute...
>>>>
>>>> Jacques
>>>>
>>>> From: "masionas" <mi...@gmail.com>
>>>>
>>>> Hi Guys,
>>>>
>>>>>
>>>>> Is Fedex integration working in the recent trunk? It used to work back
>>>>> in
>>>>> old times where the config was in the shipment.properties file. Now I am
>>>>> trying to enter config settings from Shipment Gateway Config UI under
>>>>> facility. Put Fedex account number and meter number. Then went to
>>>>> outgoing
>>>>> shipment to route segment, but it gives me error 'Fedex Shipment Gateway
>>>>> Configuration is not available'.
>>>>>
>>>>> Does anyone experience same problems?
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://ofbiz.135035.n4.nabble.****com/Fedex-Shipment-Gateway-****
>>>>> Configuration-is-not-****available-tp3325318p3325318.****html<
>>>>> http://ofbiz.135035.n4.**nabble.com/Fedex-Shipment-**
>>>>> Gateway-Configuration-is-not-**available-tp3325318p3325318.**html<http://ofbiz.135035.n4.nabble.com/Fedex-Shipment-Gateway-Configuration-is-not-available-tp3325318p3325318.html>
>>>>>>
>>>>>
>>>>> Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: Fedex Shipment Gateway Configuration is not available
Posted by Mike <mz...@gmail.com>.
Thanks Jacques . I was wondering. Is it more common to deploy OFBiz
systems using manually entered shipping rules?
On Tue, Jun 5, 2012 at 2:28 AM, Jacques Le Roux <
jacques.le.roux@les7arts.com> wrote:
> Hi Mike,
>
> I was supposed to work on it for a client, but finally did not implement
> it.
> When I do such stuff mysfelf (even for a client) I try to do it
> contribution minded (if the client agree).
> I don't know if the client finally did it (I did the research and a bit of
> the pre-analysis) but they did not contribute it
>
> Jacques
>
> Mike wrote:
>
>> Reviving Thread:
>>
>> Jacques, can you tell me the status of Fedex integration today? Does it
>> still not work?
>>
>> Thanks
>>
>>
>> On Sat, Feb 26, 2011 at 1:08 AM, Jacques Le Roux <
>> jacques.le.roux@les7arts.com> wrote:
>>
>> The Fedex "API" has changed, here is an analysis I did for a client in
>>> August
>>>
>>> <<OFBiz
>>>
>>> OFBiz is using the "old" way: the "Ship Manager Direct XML API"
>>> (introduced in August 2007).
>>> Currently in OFBiz there are entities for shipment carriers
>>> (ShipmentTypeData.xml) but they are not yet used
>>> https://cwiki.apache.org/****confluence/display/OFBIZ/**<https://cwiki.apache.org/**confluence/display/OFBIZ/**>
>>> Third+Party+Payment+and+****Shipment+Configuration#**
>>> ThirdPartyPaymentandShipmentCo****nfiguration-****ShipmentConfiguration<
>>> https://**cwiki.apache.org/confluence/**display/OFBIZ/Third+Party+**
>>> Payment+and+Shipment+**Configuration#**ThirdPartyPaymentandShipmentCo**
>>> nfiguration-**ShipmentConfiguration<https://cwiki.apache.org/confluence/display/OFBIZ/Third+Party+Payment+and+Shipment+Configuration#ThirdPartyPaymentandShipmentConfiguration-ShipmentConfiguration>
>>> >
>>>
>>> Though some are set in DemoShipping.xml
>>> There is also a ShipmentTypeData.xml file but I did not dig in.
>>> I'd have to check it closely but it looks like OOTB OFBiz handles only
>>> one
>>> item by order so far.
>>>
>>> Fedex
>>>
>>> Fedex has deprecated the API used by OFBiz and recommend now to use
>>> rather
>>> "FedEx Web Services":
>>> http://fedex.com/us/developer/****product/migration.html<http://fedex.com/us/developer/**product/migration.html>
>>> <http:**//fedex.com/us/developer/**product/migration.html<http://fedex.com/us/developer/product/migration.html>
>>> >
>>>
>>> Abstract: <<Since FedEx Web Services was introduced in August 2007, the
>>> FedEx Ship Manager® API and FedEx Ship Manager® Direct
>>> solutions were placed in containment and no new services or features have
>>> been added. On May 31, 2012, FedEx will retire our legacy
>>> FedEx Ship Manager API and FedEx Ship Manager Direct backend systems.
>>> Customers that have not transitioned to FedEx Web Services or
>>> another FedEx electronic shipping solution by this date will not be able
>>> to submit FedEx Ship Manager API or FedEx Ship Manager
>>> Direct transactions through the FedEx systems.>>
>>> FAQ:
>>> http://images.fedex.com/us/****developer/downloads/****migrationFAQ.pdf<http://images.fedex.com/us/**developer/downloads/**migrationFAQ.pdf>
>>> <http://**images.fedex.com/us/developer/**downloads/migrationFAQ.pdf<http://images.fedex.com/us/developer/downloads/migrationFAQ.pdf>
>>> >
>>>
>>>
>>> Axis: "FedEx Web Services" were tested with jdk 1.5 and are using Axis
>>> 1.4. In OFBiz Axis 1.4 has been replaced by Axis 2 some
>>> months ago. I can't still see the Axis 1.4 jar though and I'm not quite
>>> sure yet if it's still usable. Anyway does not sound like a
>>> big deal since "FedEx Web Services" needs more than Axis 1.4 jar files
>>> and
>>> some are not in OFBiz.
>>> There are both SOAP and non SOAP (using HTTP POST) services, WSDL is used
>>> in both cases but they don't use the same Error Handling.
>>> There are
>>> * Standard services for general use and do not require certification.
>>> * Advanced services for proprietary developers and will require
>>> certification prior to production launch.
>>> Both Web services levels offer sample code in Java, C#, C++, VB.Net and
>>> PHP programming languages.
>>> I don't think we need certification except if we want to offer Fedex
>>> sercices as a 3rd party and be a "FedEx compatible solution
>>> provider"
>>> http://www.fedex.com/us/****developer/product/****requirements.html<http://www.fedex.com/us/**developer/product/**requirements.html>
>>> <http://www.**fedex.com/us/developer/**product/requirements.html<http://www.fedex.com/us/developer/product/requirements.html>
>>> >
>>>
>>>
>>> Fedex provides 4 types of web services
>>> * Web Services for Shipping: Shipment/Label/Express Tag (create, cancel,
>>> validate), Rate, Package Movement, Tracking and Visibility,
>>> Address validation, Courier Dispatch Service, Return (print label from
>>> AMI
>>> site), ...
>>> * Web Services for Office and Print: enable users to manage the creation,
>>> configuration and submission of FedEx Office digital print
>>> order
>>> * Ship Manager Server: a solution for high-volume shippers who need to
>>> process, label, and ship large volumes of packages. It allows
>>> full integration of the FedEx service modules - tracking, rating and
>>> routing - with a company's existing computer systems.
>>> * Plug-ins: for customers that need quick Web based solutions with
>>> minimal
>>> IT/Developer Resources (there are also related
>>> Integration Tools: Web Integration Wizard and QuickShip modules)
>>>
>>> At 1st glance it looks like we need at least FedEx "Web Services for
>>> Shipping", Integration Tools do not seem to qualify. But when I
>>> digged a bit deeper I found that only "Ship Manager Server" has service
>>> guarantee for high volume and network reliability
>>> <<The decision to use FedEx Web Services is an easy one
>>> We recommend FedEx Web Services as your integration solution if your
>>> business has:
>>> * Online transactions that need immediate response.
>>> * Low to medium transaction volume.
>>> If your business has a high transaction volume, we recommend FedEx Ship
>>> Manager® Server.>>
>>> http://www.fedex.com/us/****developer/product/solutions.****html<http://www.fedex.com/us/**developer/product/solutions.**html>
>>> <http://www.fedex.com/us/**developer/product/solutions.**html<http://www.fedex.com/us/developer/product/solutions.html>
>>> >
>>>
>>> So eventually it looks like "Ship Manager Server" is more appropriate,
>>> but
>>> this is not my decision of course.
>>>
>>> These links are useful for an overview:
>>> http://www.fedex.com/us/****services/ataglance.html<http://www.fedex.com/us/**services/ataglance.html>
>>> <http:/**/www.fedex.com/us/services/**ataglance.html<http://www.fedex.com/us/services/ataglance.html>
>>> >
>>> http://fedex.com/us/solutions/****overview.html<http://fedex.com/us/solutions/**overview.html>
>>> <http://fedex.**com/us/solutions/overview.html<http://fedex.com/us/solutions/overview.html>
>>> **>
>>> Interactive guide: http://fedex.com/us/helpguide/****index.html<http://fedex.com/us/helpguide/**index.html>
>>> <http://fedex.com/**us/helpguide/index.html<http://fedex.com/us/helpguide/index.html>
>>> >
>>>
>>> This last one is rather long but looks like user references
>>> (functionalities) and more usable for Fedex beginners (devs included):
>>> http://images.fedex.com/us/****services/pdf/Service_Guide_****2010.pdf<http://images.fedex.com/us/**services/pdf/Service_Guide_**2010.pdf>
>>> <http://images.fedex.**com/us/services/pdf/Service_**Guide_2010.pdf<http://images.fedex.com/us/services/pdf/Service_Guide_2010.pdf>
>>> >
>>>
>>>
>>> Finally, I must say it's not easy to find your way there, but OFBiz is
>>> the
>>> same when you begin...
>>>
>>> I will see now what the community thinks about it. If OK on both side I'd
>>> like to introduce the "FedEx Web Services" in OFBiz...>>
>>>
>>> HTH, feel free to contribute...
>>>
>>> Jacques
>>>
>>> From: "masionas" <mi...@gmail.com>
>>>
>>> Hi Guys,
>>>
>>>>
>>>> Is Fedex integration working in the recent trunk? It used to work back
>>>> in
>>>> old times where the config was in the shipment.properties file. Now I am
>>>> trying to enter config settings from Shipment Gateway Config UI under
>>>> facility. Put Fedex account number and meter number. Then went to
>>>> outgoing
>>>> shipment to route segment, but it gives me error 'Fedex Shipment Gateway
>>>> Configuration is not available'.
>>>>
>>>> Does anyone experience same problems?
>>>>
>>>> --
>>>> View this message in context:
>>>> http://ofbiz.135035.n4.nabble.****com/Fedex-Shipment-Gateway-****
>>>> Configuration-is-not-****available-tp3325318p3325318.****html<
>>>> http://ofbiz.135035.n4.**nabble.com/Fedex-Shipment-**
>>>> Gateway-Configuration-is-not-**available-tp3325318p3325318.**html<http://ofbiz.135035.n4.nabble.com/Fedex-Shipment-Gateway-Configuration-is-not-available-tp3325318p3325318.html>
>>>> >
>>>>
>>>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>>>
>>>
Re: Fedex Shipment Gateway Configuration is not available
Posted by Jacques Le Roux <ja...@les7arts.com>.
Hi Mike,
I was supposed to work on it for a client, but finally did not implement it.
When I do such stuff mysfelf (even for a client) I try to do it contribution minded (if the client agree).
I don't know if the client finally did it (I did the research and a bit of the pre-analysis) but they did not contribute it
Jacques
Mike wrote:
> Reviving Thread:
>
> Jacques, can you tell me the status of Fedex integration today? Does it
> still not work?
>
> Thanks
>
>
> On Sat, Feb 26, 2011 at 1:08 AM, Jacques Le Roux <
> jacques.le.roux@les7arts.com> wrote:
>
>> The Fedex "API" has changed, here is an analysis I did for a client in
>> August
>>
>> <<OFBiz
>>
>> OFBiz is using the "old" way: the "Ship Manager Direct XML API"
>> (introduced in August 2007).
>> Currently in OFBiz there are entities for shipment carriers
>> (ShipmentTypeData.xml) but they are not yet used
>> https://cwiki.apache.org/**confluence/display/OFBIZ/**
>> Third+Party+Payment+and+**Shipment+Configuration#**
>> ThirdPartyPaymentandShipmentCo**nfiguration-**ShipmentConfiguration<https://cwiki.apache.org/confluence/display/OFBIZ/Third+Party+Payment+and+Shipment+Configuration#ThirdPartyPaymentandShipmentConfiguration-ShipmentConfiguration>
>> Though some are set in DemoShipping.xml
>> There is also a ShipmentTypeData.xml file but I did not dig in.
>> I'd have to check it closely but it looks like OOTB OFBiz handles only one
>> item by order so far.
>>
>> Fedex
>>
>> Fedex has deprecated the API used by OFBiz and recommend now to use rather
>> "FedEx Web Services":
>> http://fedex.com/us/developer/**product/migration.html<http://fedex.com/us/developer/product/migration.html>
>> Abstract: <<Since FedEx Web Services was introduced in August 2007, the
>> FedEx Ship Manager® API and FedEx Ship Manager® Direct
>> solutions were placed in containment and no new services or features have
>> been added. On May 31, 2012, FedEx will retire our legacy
>> FedEx Ship Manager API and FedEx Ship Manager Direct backend systems.
>> Customers that have not transitioned to FedEx Web Services or
>> another FedEx electronic shipping solution by this date will not be able
>> to submit FedEx Ship Manager API or FedEx Ship Manager
>> Direct transactions through the FedEx systems.>>
>> FAQ:
>> http://images.fedex.com/us/**developer/downloads/**migrationFAQ.pdf<http://images.fedex.com/us/developer/downloads/migrationFAQ.pdf>
>>
>> Axis: "FedEx Web Services" were tested with jdk 1.5 and are using Axis
>> 1.4. In OFBiz Axis 1.4 has been replaced by Axis 2 some
>> months ago. I can't still see the Axis 1.4 jar though and I'm not quite
>> sure yet if it's still usable. Anyway does not sound like a
>> big deal since "FedEx Web Services" needs more than Axis 1.4 jar files and
>> some are not in OFBiz.
>> There are both SOAP and non SOAP (using HTTP POST) services, WSDL is used
>> in both cases but they don't use the same Error Handling.
>> There are
>> * Standard services for general use and do not require certification.
>> * Advanced services for proprietary developers and will require
>> certification prior to production launch.
>> Both Web services levels offer sample code in Java, C#, C++, VB.Net and
>> PHP programming languages.
>> I don't think we need certification except if we want to offer Fedex
>> sercices as a 3rd party and be a "FedEx compatible solution
>> provider"
>> http://www.fedex.com/us/**developer/product/**requirements.html<http://www.fedex.com/us/developer/product/requirements.html>
>>
>> Fedex provides 4 types of web services
>> * Web Services for Shipping: Shipment/Label/Express Tag (create, cancel,
>> validate), Rate, Package Movement, Tracking and Visibility,
>> Address validation, Courier Dispatch Service, Return (print label from AMI
>> site), ...
>> * Web Services for Office and Print: enable users to manage the creation,
>> configuration and submission of FedEx Office digital print
>> order
>> * Ship Manager Server: a solution for high-volume shippers who need to
>> process, label, and ship large volumes of packages. It allows
>> full integration of the FedEx service modules - tracking, rating and
>> routing - with a company's existing computer systems.
>> * Plug-ins: for customers that need quick Web based solutions with minimal
>> IT/Developer Resources (there are also related
>> Integration Tools: Web Integration Wizard and QuickShip modules)
>>
>> At 1st glance it looks like we need at least FedEx "Web Services for
>> Shipping", Integration Tools do not seem to qualify. But when I
>> digged a bit deeper I found that only "Ship Manager Server" has service
>> guarantee for high volume and network reliability
>> <<The decision to use FedEx Web Services is an easy one
>> We recommend FedEx Web Services as your integration solution if your
>> business has:
>> * Online transactions that need immediate response.
>> * Low to medium transaction volume.
>> If your business has a high transaction volume, we recommend FedEx Ship
>> Manager® Server.>>
>> http://www.fedex.com/us/**developer/product/solutions.**html<http://www.fedex.com/us/developer/product/solutions.html>
>> So eventually it looks like "Ship Manager Server" is more appropriate, but
>> this is not my decision of course.
>>
>> These links are useful for an overview:
>> http://www.fedex.com/us/**services/ataglance.html<http://www.fedex.com/us/services/ataglance.html>
>> http://fedex.com/us/solutions/**overview.html<http://fedex.com/us/solutions/overview.html>
>> Interactive guide: http://fedex.com/us/helpguide/**index.html<http://fedex.com/us/helpguide/index.html>
>> This last one is rather long but looks like user references
>> (functionalities) and more usable for Fedex beginners (devs included):
>> http://images.fedex.com/us/**services/pdf/Service_Guide_**2010.pdf<http://images.fedex.com/us/services/pdf/Service_Guide_2010.pdf>
>>
>> Finally, I must say it's not easy to find your way there, but OFBiz is the
>> same when you begin...
>>
>> I will see now what the community thinks about it. If OK on both side I'd
>> like to introduce the "FedEx Web Services" in OFBiz...>>
>>
>> HTH, feel free to contribute...
>>
>> Jacques
>>
>> From: "masionas" <mi...@gmail.com>
>>
>> Hi Guys,
>>>
>>> Is Fedex integration working in the recent trunk? It used to work back in
>>> old times where the config was in the shipment.properties file. Now I am
>>> trying to enter config settings from Shipment Gateway Config UI under
>>> facility. Put Fedex account number and meter number. Then went to outgoing
>>> shipment to route segment, but it gives me error 'Fedex Shipment Gateway
>>> Configuration is not available'.
>>>
>>> Does anyone experience same problems?
>>>
>>> --
>>> View this message in context:
>>> http://ofbiz.135035.n4.nabble.**com/Fedex-Shipment-Gateway-**
>>> Configuration-is-not-**available-tp3325318p3325318.**html<http://ofbiz.135035.n4.nabble.com/Fedex-Shipment-Gateway-Configuration-is-not-available-tp3325318p3325318.html>
>>> Sent from the OFBiz - User mailing list archive at Nabble.com.