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 » OS Environment Variables in File Paths

Post new topic  Reply to topic
 OS Environment Variables in File Paths « View previous topic :: View next topic » 
Author Message
hascheidl
PostPosted: Fri Jun 16, 2006 8:23 am    Post subject: OS Environment Variables in File Paths Reply with quote

Novice

Joined: 05 Jun 2006
Posts: 15

Does anybody knows if it is possible to use a windows environment variable in the "file path" property of a Trace node? I couldn't at first, maybe I did something wrong.
If not, maybe I can put its value in a message flow Environment variable, before the message enters the Trace node, and access the ${Environment.Variables.nono}... Will it work?
_________________
Half
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Jun 16, 2006 1:34 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

No, it's not possible in either way.

The Trace node, in all versions that I'm aware of, does not do any interpolation at all of the file name from the properties, it merely passes it directly to a C file open call. This call will not do any shell expansion, so environment variables do not come into effect.

The Trace node uses a static file path, always. It is not in any way designed to act as a file output node, and any attempts to make it work as one are doomed to failure.

If you want to write messages to a file, then you should use a Java compute node.

If you want to do enterprise level file transport with MQ and with Broker, you should evaluate a number of products that act in that space, including the File Extender nodes.

Please note that "write messages to a file" is a completely different thing than "enterprise level file transport", such that doing the first does not in anyway accomplish the second.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
hascheidl
PostPosted: Sat Jun 17, 2006 11:48 am    Post subject: Reply with quote

Novice

Joined: 05 Jun 2006
Posts: 15

Ok, thank you. So what does it mean?

Quote:
You can use any name for the trace file. For example, c:\$user\trace\trace.log.

_________________
Half
Back to top
View user's profile Send private message
EddieA
PostPosted: Sun Jun 18, 2006 9:50 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

It means you have a directory called $user, on yor C drive, which has a subdirectory called trace, that contains a file called trace.log.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
hascheidl
PostPosted: Mon Jun 19, 2006 4:07 am    Post subject: Reply with quote

Novice

Joined: 05 Jun 2006
Posts: 15


_________________
Half
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » OS Environment Variables in File Paths
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.