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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED]UPES From Container

Post new topic  Reply to topic
 [SOLVED]UPES From Container « View previous topic :: View next topic » 
Author Message
Ratan
PostPosted: Mon Sep 22, 2003 4:43 pm    Post subject: [SOLVED]UPES From Container Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

When I am setting the UPES fully Qualified name in a Data member and setting to Execution of an Activity to UPES From Container, Workflow is throwing an Exception. The same is working if I specify just the UPES name and not the fully Qualified UPES name for PES from Container.

Am I doing anything wrong?

The exception thrown is

<![CDATA[FmcAssertionException, Condition=*** Pre-condition failed in e:\v332\src\fmcmpeid.hxx(101): name.Length() < FMC_SERVER_NAME_LENGTH]]>
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
Ratan
PostPosted: Tue Sep 23, 2003 10:42 am    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

Has anybody used UPES 'From Container' setting for an activity?
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
jmac
PostPosted: Tue Sep 23, 2003 2:13 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Ratan:

Not me, that's why I haven't replied . The only thing that I can see when taking a quick look is that the order is ServerName.SYSTEMNAME.SysGroupName.... I know if I did this I probably would assume that it was ServerName.SysGroupName.SYSTEMNAME.... Maybe you did too?
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Ratan
PostPosted: Tue Sep 23, 2003 3:23 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

I used ServerName.SystemName.SysGroupName because when you select a UPES that is the FullyQualifiedName.

Looks like I should open a PMR for this.

Thanks John.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
manoj
PostPosted: Thu Sep 25, 2003 12:05 pm    Post subject: Reply with quote

Master

Joined: 30 Jan 2002
Posts: 237
Location: Virgina

Hi,
Try using the high level name of the Upes server...do not specify the fully qulaified name.. this will help u to achieve load balancing when you 've multiple systems.

eg: if ur upes defenition is UPESSVR.FMCSYS.FMCGRP.

use UPESSVR in the activity ...
_________________
-manoj
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
Ratan
PostPosted: Thu Sep 25, 2003 12:18 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

We already do that. It helps in load balancing but there are certain scenarios where it completely screws up and that is why we are trying to specify UPES from container (different UPES for different systems).
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
sshaker
PostPosted: Fri Sep 26, 2003 6:56 pm    Post subject: Reply with quote

Disciple

Joined: 20 Sep 2002
Posts: 185

Hi ratan
looking at ur message it looks like the length of the UPES name is considered along with the systema and system group name (FMC_SERVER_NAME_LENGTH) which will be more than the prescribed limit for sever name .. i guess the limit as 8 chars..

may be u will be able to cheat the system by making it just UPES name (without sys/sysgrp) as suggested by manoj .. and change it as required (with sys/sysgrp name) ... but i am not sure on how u will do that... can u explain what ur trying to achieve by using the value from container.. ?

if it doesnt work then the last option is to go to IBM with a PMR .. as u already thought of!

regards
_________________
shaker
Back to top
View user's profile Send private message
Ratan
PostPosted: Mon Sep 29, 2003 2:08 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

I got a workaround for my problem.

The Problem: I have 2 systems in my group A, B with the high level UPES name 'C' for both the systems. I need a Process that starts on System 'B' to finish on System 'B', but that doesnot happen when you have an Expired Activity in your process. When an activity expires the rest of the execution of activities moves to UPES 'c' on the Primary System.

So I need Different UPES name defined for activities in a process that starts on System A and System B.

I thought I could solve this by Specifying the fully qualified UPES name 'from container' and my first activity setting this, but evidently it did not. So I am having 2 UPESes defined per system, both pointing to the same Queue and QM. one definition will have the same name for both the Systems (this is for load balancing the first activity). Other UPES definition will be different for both systems and this will be set for rest of the UPES activities.

Thanks Guys.
_________________
-Ratan
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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED]UPES From Container
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.