ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » New BAPI Changes not reflected

Post new topic  Reply to topic
 New BAPI Changes not reflected « View previous topic :: View next topic » 
Author Message
kirankinnu
PostPosted: Thu Aug 02, 2012 11:14 am    Post subject: New BAPI Changes not reflected Reply with quote

Centurion

Joined: 12 Jun 2004
Posts: 128
Location: Chicago, IL

Hi All,
We are working on WMB v7 and using SAPRequest node to make BAPI calls. We are able to successfully make the BAPI call. The issue is, when ever there is a BAPI change, we have to restart the Broker for the changes to get reflected. If we do not restart, the SAPRequest is somehow making a call to Old BAPI code. We checked with SAP folks and they couldn't help us. This never happened in V6.1. We noticed this issue only after migrating to V7.

Is there any configuration on broker end, which tells the SAP to hold a connection and use the BAPI. Any thoughts would be appreciated.

Thanks,
Kiran
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Aug 02, 2012 8:38 pm    Post subject: Re: New BAPI Changes not reflected Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

kirankinnu wrote:
Hi All,
We are working on WMB v7 and using SAPRequest node to make BAPI calls. We are able to successfully make the BAPI call. The issue is, when ever there is a BAPI change, we have to restart the Broker for the changes to get reflected. If we do not restart, the SAPRequest is somehow making a call to Old BAPI code. We checked with SAP folks and they couldn't help us. This never happened in V6.1. We noticed this issue only after migrating to V7.

Is there any configuration on broker end, which tells the SAP to hold a connection and use the BAPI. Any thoughts would be appreciated.

Thanks,
Kiran


SAP JCO has a respository that caches metadata about BAPI's and IDOC's.
Typically it gets initialized with the first call to a specific BAPI or IDOC etc...
I would expect that the same way you deploy a new version of the BAPI or IDOC, you will stop and restart the flow...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » New BAPI Changes not reflected
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.