MQSeries.net :: View topic - Using the NEON Formatter Node in an MQSI Message Flow

mehedih · Posted: Tue Nov 13, 2001 3:23 pm Post subject:

Hi Folks,

I'm trying to use Using the NEON Formatter Node is an MQSI Message Flow.
MQSI can't find the MQSIruleng.mpf file even though the MQSI_PARAMETERS_FILE system variable is set to the right path.

MQSIruleng.mpf as it stands (Exhibit B)
(the file is in the c:Program FileIBM MQSeries Integrator 2.0bin directory)

I set the MSQI_PARAMETERS_FILE system environment variable to value
(c:Program FileIBM MQSeries Integrator 2.0bin)

The message flow (NEOFLOW1) has three nodes
- MQinput(INX) - NeonFormatter - MQoutout(OUTX).
It doesn't work .The event log shows the following message (Exhibit A).

Tried another approach (MQSIruleng -install).The install works
but the MQSIruleng -start doesn't and there aren't any associated error messages.

Any suggestions

***********************************************E X H I B I T A *********
SAMPLE_BROKER.default )
Cannot open NEON parameters file 'C:Program FilesIBM MQseries Integrator 2.0bin'
In order to parse messages using the NEON parser,
the MQSI_PARAMETERS_FILE environment variable must
give the location of the parameters file giving the connection
information for the database containing the NEON format definitions.
Correct the value of the MQSI_PARAMETERS_FILE environment
variable to contain
the full path to the NEON parameters file.
On an NT system it
will be necessary to reboot the machine in order for the
******************************************************************

***********E X H I B I T B ********************************************************
###########################################################################
# #
# This is the tunable parameters file for MQSIruleng... #
# #
# Comments must have a # in the first column; trailing comments forbidden #
# Names must be separated from the equals sign by whitespace #
# Values must be separated from the equals sign by whitespace #
# Values may not contain whitespace #
# #
# Note that any values in this parameter file will override defaults #
# established by the daemon! #
# #
###########################################################################

[Queues]
# parameters related to queues, MQSeries control, and rules engine control...

# Alternate User Authority flag
CredentialsEnabled = 0

## MQSeries queue manager name...defaults to default queue manager
#QueueManagerName = MQI
QueueManagerName = QM_xind_y4howpbfu3

# number of replay/retry attempts before failed message is sent to
# the failure queue (zero indicates no replays allowed)
MaxBackoutCount = 0

# these three queue names are mandatory!
InputQueueName = INX
NoHitQueueName = FAILURE1
FailureQueueName = FAILURE2

# rules default application group and message type values (mandatory)
DefaultAppGroup = MQ66
DefaultMsgType = MQ66InMsg

#[Queue Handle Cache]
## parameters used to control the output queue handle cache...
#MaxHandles = 25
#PurgeInterval = 30

[Logging]
# log file control..."LogFileName" is the file specification for the log,
# and valid "LogLevel" settings are:
# 3 - log only fatal errors
# 2 - log errors, and fatal errors
# 1 - log warnings, errors, and fatals
# 0 - log informationals, warnings, errors, and fatals
LogFileName = mqsiruleng.log
LogLevel = 0

[Rules Database Connection]
#
# Rules and Formatter database connection information (all fields mandatory
# except "DatabaseInstance" which is not required for use with Oracle)
#
ServerName = MQSNNEON
UserId = xxxxxxxx
Password = xxxx
DatabaseInstance = ???
#
# DatabaseType is a numeric with these values:
# SYBASE (CTLIB bindings) = 1
# SYBASE (DBLIB bindings) = 2
# MSSQL = 4
# DB2 = 5
# ODBC = 6
# ORACLE (version 7.x) = 8
# ORACLE (version 8.x) = 9
#
DatabaseType = 6

#
# end of file!
#

***************************************************************

Regards

Mehedi Hashir
mhashir@hotmail.com

[ This Message was edited by: mehedih on 2001-11-13 15:24 ]