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 » Reg : Subflow

Post new topic  Reply to topic Goto page Previous  1, 2
 Reg : Subflow « View previous topic :: View next topic » 
Author Message
Vitor
PostPosted: Fri Jul 26, 2013 9:20 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

lancelotlinc wrote:
In banking and insurance (my last two assignments), developers are explicitly prohibited from accessing any PROD artifact.


Who said the developer was doing it directly?

I indicate in any earlier post that a user trace might be in response to a production ticket, which could be the support team running it on behalf of a developer, or a developer running the user trace in Prod using a "Break-The-Glass" id activated in response to the ticket.

In all my I.T. years, I've had 2 manufactoring assignments, the rest were in banking & insurance (USA, UK & Australia) so I know all about access controls and spend a good part of my time developing and enforcing them. I currently work for a bank (not as well known or as large as the insurance company you work for) and we have both Prod access methods available to us, with guidance on which is appropriate in what circumstance.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Jul 26, 2013 9:23 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Vitor wrote:
lancelotlinc wrote:
In banking and insurance (my last two assignments), developers are explicitly prohibited from accessing any PROD artifact.


Who said the developer was doing it directly?

I indicate in any earlier post that a user trace might be in response to a production ticket, which could be the support team running it on behalf of a developer, or a developer running the user trace in Prod using a "Break-The-Glass" id activated in response to the ticket.

In all my I.T. years, I've had 2 manufactoring assignments, the rest were in banking & insurance (USA, UK & Australia) so I know all about access controls and spend a good part of my time developing and enforcing them. I currently work for a bank (not as well known or as large as the insurance company you work for) and we have both Prod access methods available to us, with guidance on which is appropriate in what circumstance.


We wouldn't have access to any log or artifact. We would have to ask someone else to get the artifact then ask specific questions, which the artifact viewer would then answer. Its much better to have your code working before it gets to PROD. Hence, designing and implementing in a proactive sort of way.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Fri Jul 26, 2013 10:06 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

lancelotlinc wrote:
Its much better to have your code working before it gets to PROD. Hence, designing and implementing in a proactive sort of way.


Of course it's better to have working code. But because I lack both your infalibility (as do my development customers, some of whom appear to lack competance) and (as previously discussed) the massively funded and tightly controlled development environment with which you are blessed that prevents any form of production outage, we have proactively designed and implemented a system by which we can identify and resolve code (and other) issues in Prod.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Abhinay185127
PostPosted: Sun Jul 28, 2013 9:54 pm    Post subject: Reply with quote

Acolyte

Joined: 20 May 2013
Posts: 58

Hi ,

I was using debugger mode and the second time it was not invoking the subflow.

Soap Input --- Flow order --- 1 terminal--- Compute(Sets environment for logging) -- Logging subflow --- Flow Order --- 2 terminal --- Main Flow Compute(maps and transforms) PROPAGATING to OUT1 terminal -- Logging subflow --- thean again main flow and so on.....

So the secong time it is not going inside the sublow.

Although i was able to resolve the issue. I converted the .subflow to .msgflow and its working absolutely fine now. But really don't know the reason.
Back to top
View user's profile Send private message
goffinf
PostPosted: Sun Jul 28, 2013 10:16 pm    Post subject: Reply with quote

Chevalier

Joined: 05 Nov 2005
Posts: 401

Abhinay185127 wrote:

I converted the .subflow to .msgflow and its working absolutely fine now. But really don't know the reason.


There are a number of known issues with using subflows under v8. Your comment above indicates you should upgrade your run-time and toolkit to fix pack 2 (8.0.0.2) and apply iFix 001 to your toolkit.

Fraser.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Reg : Subflow
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.