Configuring the Production
This chapter describes the process of creating and configuring an X12 production.
Be sure to perform all tasks in the same namespace that contains your production. When you create rule sets and transformations do not use reserved package names; see “Reserved Package Names” in Developing Productions.
Also see “Overriding the Validation Logic” in Using Virtual Documents in Productions.
Creating a new X12 Production
You can add X12 components to an already existing production. However, if you want to create a new production explicitly for handling X12, follow the steps below.
In the Management Portal, switch to the appropriate namespace.
To do so, click Switch in the title bar, click the namespace, and click OK.
Click Production and then click Go.
InterSystems IRIS® then displays the last production you accessed, within the Production Configuration page.
Click the Actions tab on the Production Settings menu.
Click New to invoke the Production Wizard.
Enter a Package Name, Production Name, and Description.
Choose the Generic production type and click OK.
InterSystems IRIS creates a blank production from which you can add components such as business services, business processes, and business operations. See the sections below for more details.
As you build your production, it frequently happens that while configuring one component you must enter the name of another component that you have not yet created. A clear naming convention is essential to avoid confusion. For suggestions, see “Naming Conventions” in Best Practices for Creating Productions. For rules, see “Configuration Names,” in Configuring Productions.
Adding an X12 Business Service
Add one X12 business service for each application or source from which the production receives X12 documents.
To add an X12 business service to a production:
Click the X12 Input tab.
Click one of the following from the Input type list:
In the X12 Service Name field, type the name of this business service.
In the X12 Service Target area, select one of the following options:
Create New Router — InterSystems IRIS adds a business process to the production and configures the business service to use it as a target. You can edit the business process details later.
Choose From List — In this case, also select an existing business host from the drop-down list.
None for Now — Do not specify a target for this business service. If you make this selection, ensure that you specify a target later.
Adding an X12 Business Process
To add an X12 business process to a production:
Click the X12 Router tab; the router class defaults to EnsLib.EDI.X12.MsgRouter.RoutingEngine.
For Routing Rule Name, do one of the following:
Select an existing routing rule from the Routing Rule Name drop-down list.
Select Auto-Create Rule and type a rule name into Routing Rule Name. In this case, the wizard creates the routing rule class in the same package as the production.
Later you must edit the routing rule and add your logic to it.
For X12 business process Name, type the name of this business process.
Ensure that your X12 business service is connected to the new X12 Business Process. To connect the process:
Select your X12 business service.
Click the Settings tab and open the Basic Settings menu in the menu to the right of the screen.
Enter the name of the new X12 business process in the Target Config Names field.
Configure additional settings of the business process, as needed. For details, see “Settings for X12 Business Processes”.
Adding an X12 Routing Rule
For general information on defining business rules, see Developing Business Rules.
When you create an X12 routing rule:
On the general tab, Rule Type should be Virtual Document Message Routing Rule. This choice sets the following options:
Rule Assist Class should be EnsLib.MsgRouter.VDocRuleAssist
Context Class should be EnsLib.MsgRouter.VDocRouting Engine
In the constraint for a rule, specify Message Class as EnsLib.EDI.X12.Document.
In all other respects, the structure and syntax for both types of rule set are the same.
Adding an X12 Business Operation
To send X12 messages from a production to a file or application, you must add an X12 business operation. Add an X12 business operation for each output destination.
You might also want to add business operations to handle bad messages (for background, see “Business Processes for Virtual Documents” in Using Virtual Documents in Productions).
To add an X12 business operation to a production:
Click the X12 Output tab.
Click one of the following from the Output type list:
For X12 Operation Name, type the name of this business operation.
Ensure that the business operation is connected to the relevant business services or business process
For a routing rule, enter the name of your X12 business operation in the Target field of the routing rule set.
If your design uses a pass-through interface that simply relays messages from the incoming business service to the outgoing business operation, enter the name of your X12 business operation in the Target Config Names field of the X12 business service.
Configure additional settings of the business operation, as needed. For details, see “Settings for X12 Business Operations”.
If you want the production to send data that is not an X12 message, see “Defining Business Operations” in Developing Productions. Also see “Connectivity Options” in Introducing Interoperability Productions.