Configuring integration nodes
Create and configure the integration node that you want on the operating system of your choice.
Before you begin
Ensure that the following requirements are met:
- Your user ID has the correct authorizations to perform the task. The authorizations are defined in Security requirements for administrative tasks.
On Windows:
you have created a user ID to be used as the service user ID. You
specify this ID when you create the integration node; it is used to
run the integration node.For more information about user ID authorization and creation, refer to Planning for security.
- You have initialized the command environment on distributed systems; see Setting up a command environment.
About this task
When you have created your physical components, you can administer your test and production environments programmatically by using the IBM Integration API.
This collection of tasks uses specific resource names and user IDs. These names are examples only; you can use your own names. Follow existing naming conventions for IBM MQ and other resources.
Procedure
- Create an integration node by following in the instructions in Creating an integration node.
- Verify that the integration node is created by following the instructions in Verifying an integration node.
- Modify the integration node by following the instructions in Configuring an integration node by modifying the node.conf.yaml file.
- (Optional) If you are developing message flows that include resources such as the WebSphere® Adapters nodes, IMS nodes, or the CICSRequest node, you must set up your environment to support these applications. Details of the setup that you require is in Configuring the environment to access external applications and resources.
- (Optional) If you are working with web services message flows and want to ensure reliable messaging, you can configure WS-RM using policy sets. See Web Services Reliable Messaging.
- (Optional) You can use WS-Security with your web services message flows to provide quality of protection through message integrity, message confidentiality, and single message authentication. See WS-Security.