0% found this document useful (0 votes)
110 views6 pages

APP Connect Questions

The document discusses questions about the IBM App Connect integration node. It covers topics like supported message formats, enabling security, handling compressed messages, schema validations, timeouts, asynchronous responses, file folders, polling, retries, excluding patterns, size limits, remote connections, scan delay, transaction modes, end of data processing, and differences between various node types.

Uploaded by

kandula nagababu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
110 views6 pages

APP Connect Questions

The document discusses questions about the IBM App Connect integration node. It covers topics like supported message formats, enabling security, handling compressed messages, schema validations, timeouts, asynchronous responses, file folders, polling, retries, excluding patterns, size limits, remote connections, scan delay, transaction modes, end of data processing, and differences between various node types.

Uploaded by

kandula nagababu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Assessment-2

1. What type’s languages supported httpinput node

 DFDL
 XMLNSC
 JSON
 BLOB
 MIME
 XMLNS
 MRM

2. if we want to provide security what is the procedure to provide it

Administration security is an optional feature of the integration node; it is not enabled by


default. You can enable administration security and select the required authorization mode
by using the mqsichangefileauth command.

3. if compressed message come how to handle?

4. xsd validations

5. validations ondemand and below

6. timeout and different error responses

7. scenarion when multiple httpreply nodes

8. below ondemand, what are those checkpoints

9. how to strip one element

10. how to identify asynchronous response which response (uniq identifier)

11. file folders explanation

12. poling supported

13. retry mechanishm

14. exclude pattern

15. recodrs and elements, max size,

16. remote connections and ports transfers

17. what is scandelay

18. transaction mode

19. end of data terminal use, data is comming or not

20. remote ftp


21. What are the file output terminals, what is the endofdata terminal tree structure/

Input terminals: In terminal and Finish file terminal

The main difference between these two modes is when the file is closed. In "In Terminal"
mode, the file is closed after each message is written to it. In "Finish File Terminal" mode, the
file is closed only after all the messages have been written to it.

main difference between "In Terminal" mode and "Finish File Terminal" mode is the timing of
the file close operation. "In Terminal" mode closes the file after each message, while "Finish
File Terminal" mode closes the file only after all messages have been written.

Out terminals: Failure, Out, EndofData

Need to do practical about Endofdata

22. How to do mq connection through command, different connections

For MQ Connection: INODE with a queue manager that is called ACEQMGR


Mqsicreatebroker INODE –I wbrkuid –a wbrkpw –q ACEQMGR

Ref: https://www.ibm.com/docs/en/app-connect/11.0.0?topic=node-creating-integration-by-using-command-line

mqsichangebroker IBNODE –q IBQMGR

Ref: https://www.ibm.com/docs/en/integration-bus/10.0?topic=command-mqsichangebroker-linux-unix-systems

Different Connections:

One is directly MQinput node place we can able to mention the MQ Queue Manager name

Second one is we can Modify the node.yaml file MQ properties place uncomment and the the MQ
Queue Manager name

Third one is we can assign the MQ Queue Manager name to Node

23. MQ connection types(local,remote,ccdt)

In IBM MQ, there are three types of connections: local connections, remote
connections, and client connections using a Client Channel Definition Table (CCDT).

1. Local Connection: A local connection is a connection that is established between an


MQ application and a queue manager on the same machine. Local connections are
the fastest and most efficient way to connect to an MQ queue manager.
2. Remote Connection: A remote connection is a connection that is established
between an MQ application and a queue manager on a different machine. Remote
connections require network communication and are slower than local connections.
They can be used to connect to queue managers that are located on other machines.
3. Client Connection using a CCDT: A client connection is a connection that is
established between an MQ client application and an MQ server using a Client
Channel Definition Table (CCDT). The CCDT contains information about the MQ
server, such as the host name, port number, and channel name. The CCDT can be
created and maintained using the IBM MQ Explorer or the runmqsc command-line
tool.

When using a CCDT, the MQ client application does not need to know the exact
connection details of the MQ server. Instead, it reads the connection information
from the CCDT. This makes it easier to configure and maintain the MQ client
application, especially if there are multiple MQ servers that the application needs to
connect to.

In summary, local connections are used to connect to a queue manager on the same
machine, remote connections are used to connect to a queue manager on a different
machine, and client connections using a CCDT are used to connect to an MQ server
using a predefined configuration file.

24. transaction mode in mq,order mode?

25. MQ how to keep message without delete

In the MQinput node ->Advanced->apply the check mark Browse only option

26. MQ reply and mqoutput difference

The main difference between the MQ Reply node and the MQ Output node
in IBM App Connect is their purpose and the direction of message flow.

The MQ Output node is used to send messages to an IBM MQ queue or


topic. It writes messages to a queue or topic, and the message is sent to the
target application or endpoint for processing. This node is used when you
want to send a message from your application to another application over
IBM MQ.

On the other hand, the MQ Reply node is used to send a reply message to
an IBM MQ request message that was received earlier. It is typically used in
a request-reply pattern where a message is sent to an application and that
application is expected to respond with a reply message. The MQ Reply
node is used to send the reply message back to the requester application.

Therefore, the MQ Output node is used to send messages to another


application, while the MQ Reply node is used to reply to messages received
from another application. Additionally, the MQ Output node can write
messages to a queue or topic without waiting for a reply, whereas the MQ
Reply node is specifically designed for sending reply messages to an
original request message.
27. Can we use soap node as rest

28. HTTPinput node other than blob how can we send soap

29. soap extract node, envolop node

30. localenvironment,all options in compute node

31. can i use one esql file for 3 computes

32. difference btwn failure and catch, not given connection to catch

33. fileoutput node how to overcome file overwite

34. http replay properties

35. without wsdl how to configure soapinput

36. how to change username and password with same identifier

37. failure and catches?

38. catch connect cheyakapothe m aithgadhi failure connect cheyakapothe m aithahdi

39. append kavadhante m cheyali file nodes?

40. http reply properties

41. soap wsdl kakunda cheyochaaa

42. security id pass change change cheyali ela?

43. record and element function---record definitions?

44. compute node properties validation is based on?

45. MQGet---compute----------

46. fileoutput

47. fileread----multiple file unte edhi read chestha

48. dfdl

49. xsd-namespaces---

50. wsdl---

51. logical tree structure

52. username password

53. httpcomp---name,loc,age-----httpreq accepts only 2 what should do?

54. asynch---etla telsthadhi response e request dhi ani-----unique identifier


55. queues folders--transit,archive,transitin,backout

56. polling (fileexists lo untadhi default value is 5 seconds)

57. records and elements

58. ftp ftps sftps--ports

59. scan delay

60. transaction mode---file node

61. filoe nodes endofdata?

62. remote connectivity-->;local aa leka remote?

63. fileoutput ki terminals

64. remote local eda vadthadhi?

65. command to changeproperties mq default nameMQ connection types---3types enityi?

66. transaction mode in mq? order mode?

67. mq la kelli msg del kavadhu etla?

68. mq output and reply? qname pettaradhu mq reply and end output

69. soap nodes lo rest set cheskovachaaa (yes)

70. retry mechanism exists

71. http supported msgs

72. https m chesthav?

73. compress msg handling --- compress enable

74. parsing options----and below checkboxes

75. validation and below failures?

76. compute---(2)httpreply node

77. http nodes la soap pampacha? yes cus soap is an xml

78. soap extract and soap envelope?

79. compute lo loggings

80. 1all esql file----in many compute nodes\

81. failure and catches?

82. catch connect cheyakapothe m aithgadhi failure connect cheyakapothe m aithahdi

83. append kavadhante m cheyali file nodes?

84. http reply properties

85. soap wsdl kakunda cheyochaaa


86. security id pass change change cheyali ela?

87. record and element function---record definitions?

88. compute node properties validation is based on?

You might also like