No, it is not
possible to modify the port of 'Blaze Job Monitor' application without
specifying the Hadoop Data Node 'Hostname'/'IP Address'.
'Blaze Job Monitor' URL
could be configured in 'Blaze
Job Monitor address' attribute under 'Blaze Engine' section of the Hadoop pushdown
connection. If the 'Blaze Job Monitor Address' attribute is not configured with explicit host details, 'Blaze Job Monitor' application would be starting in one of the active Hadoop data nodes during the Blaze Engine startup. By default, 9080 would be the port for the 'Blaze Job Monitor' application.
It is possible that 'Blaze Job Monitor'
application startup could fail with 'Address binding issues', if another instance of 'Blaze Job Monitor' application
is already running in the selected Hadoop data node, most possibly started along with
Blaze Engine from a different Informatica Domain or a different DIS in the same
Feature Request# BDM-29194 has already been raised for giving provision to modify the Blaze Job Monitor port without defining
Hadoop Data Node Hostname. Till the Feature Request is implemented in one of
the future versions, as a workaround, to modify the port of 'Blaze Job Monitor', you need to specify valid 'Hadoop Data Node Hostname' along with a new port number.
When we specify a
hostname for the 'Blaze Job Monitor' and
if that Hadoop data node becomes unavailable, the 'Blaze Job Monitor' component would alone
be affected and it would not get started. However, it would not impact other
service components like 'Blaze Grid Manager'/'Orchestrator' and hence, the
mappings would continue to run without any issues.
When the Blaze Job
Monitor is not running, logs could not be accessed from the Web console UI.
However, the logs could be retrieved from the HDFS location, after completion, or
from the local file system of Hadoop data node machines, if the jobs are still in progress.
For more information related to finding the location of 'Blaze Tasklet'
logs, while running/after completion, refer to the following KB articles:
FAQ: Where Blaze Tasklet logs generated during the execution of Blaze mode mappings from Informatica DEI would be stored? (KB 509515)
HOW TO: Download the Grid Tasklet logs corresponding to a mapping executed in Blaze Engine using Informatica DEI? (KB 531631)
HOW TO: Start and Stop Blaze Grid
Manager and Blaze Job Monitor Applications of Informatica DEI? (KB 521162)
FAQ: What are the pre-requisite
configurations that should be performed for executing mappings with Informatica
Blaze Engine? (KB 524728)
does not have sufficient resources for Blaze services, please decrease the
memory and CPU requirements for services. while starting Blaze Engine in
Informatica DEI (KB 533265)
What can we do to improve this information (2000 or fewer characters)