Creating and Configuring Multiple Transaction Servers per Environment

These general guidelines apply:

Production Environments
The F907* tables should remain in the System database as defined by the standard setup and configuration. Since the transaction server is designed to work with only one set of F907* tables, the normal procedure is to configure the transaction server with these system tables.
Test and Dev Environments
In order to separate Test and Dev environment transactions from Production, you can copy the F907* tables into the business data database and change the OCM mappings accordingly. A second transaction server is necessary in order to access these copied tables because, by design, each Transaction Server can only work with only one set of F907* tables.
Multiple Transaction Servers
In order to support the separation of the F907* tables per environment, you must install an additional Transaction Server per environment or environment combination. For example, if you want to isolate your Production environment and then combine your Test and Dev environments, you would need a total of two Transaction Servers. If you further wanted to separate your Test and Dev environments, you would need a total of three Transaction Servers.

Do not start any added Transaction Servers until you complete the procedure in this appendix.

To create and configure the Transaction Server per environment:

With the exception of the tables listed in the Exceptions below, copy all remaining F907* tables from the System database to the business data database.
Exceptions
The following tables are initially cached on JD Edwards EnterpriseOne service startup and contain the necessary information needed for all environments and subscribers. Therefore, these tables and their OCM mappings should remain in the System datasource:
- F90701
- F907011
- F90705

Use OCM to remap the F907* tables copied in Step 1 to the new business data database for both the system and the server map.

For example, the completed mappings might look like these:

JPY920 F90701  TBLE  System - 920 *PUBLIC AV 
JPY920 F907011 TBLE  System - 920 *PUBLIC AV 
JPY920 F907012 TBLE  System - 920 *PUBLIC AV 
JPY920 F90703  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90704  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90705  TBLE  System - 920 *PUBLIC AV 
JPY920 F90706  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90707  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F907071 TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F907072 TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90708  TBLE  Business Data - CRP *PUBLIC AV
JPY920 F90710  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90711  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90712  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90715  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90720  TBLE  Business Data - CRP *PUBLIC AV 
JPY920 F90730  TBLE  Business Data - CRP *PUBLIC AV

Activate the RT* event for added environment (for example, JPY920) in P90701 by:
- Taking the Form exit to Event Activation
- Doing an Add to add the new Event per environment
- Using the Row exit to change the status to Active
Refresh the JD Edwards EnterpriseOne server cache by restarting the EnterpriseOne services.
Add subscriber information for the added environment (for example, JPY920).
Refresh the Transaction Server cache by restarting the transaction server.
Trigger the event.
Verify the event is recorded in the F90710 Business Data Source table.
From a JD Edwards EnterpriseOne client machine, use this command to run the Table Trigger script for F90710 in the business data for the added environment (for example, PY Business Data):
<home>\system\bin32\dbtemplates.exe -create
where <home> is the installation directory of the JD Edwards EnterpriseOne Administration client that is named according to the JD Edwards EnterpriseOne release. For example, E812, E900, E910, or E920.
Verify the F986112 table is populated and the new event in F90710 has the status 3 instead of 2.