WSO2's API Vision: Unifying Control, Empowering Developers
Configuring ee (enterprise extender) between two ibm system i systems tech doc 404791135
1. IBM i Support: Software Technical Document : 404791135 http://www-912.ibm.com/s_dir/SLKBase.nsf/643d2723f2907f0b862566...
IBM Software Technical Document
_______________________________________________________________
Document Information
Document Number: 404791135
Functional Area: Communications-SNA
Subfunctional Area: AS/400-to-AS/400 Connectivity
Sub-Subfunctional Area: EE(Enterprise Extender)
OS/400 Release: V5R4M0; V5R4M5; V6R1M0; V6R1M1;
V7R1M0
Product: OS400 COMM BASE/APPN (5722SS1CM)
I5/OS (5761SS1CM)
Operating System/400 - OS400 COMM
BASE/APPN (5769SS1CM)
Product Release: N/A
_______________________________________________________________
Document Title
Configuring EE (Enterprise Extender) between Two IBM System i Systems
Document Description
This is a sample configuration for EE (Enterprise Extender) between two IBM System i5 systems at R540 or
above.
Caution: When using Enterprise Extender across a network that traverses firewalls, ensure UDP ports
12000 through 12004 are open to successfully establish a connection. In addition, if this was a migration
from IBM AnyNet to Enterprise Extender, ensure that you remove the remote configuration list entries from
the Anynet configuration.
Note: APPC device must be an independent LU; for example, LOCADR=00 or single session LUs work if a
remote configuration list entry is created on both sides along with a mode of one session limit.
SYSTEM A and SYSTEM B
Step 1: Ensure Allow HPR Transport Tower Support (ALWHPRTWR) is enabled in Network Attributes.
a To view the parameter: DSPNETA
b To change the value: CHGNETA ALWHPRTWR(*YES)
Step 2: Display the Network Attributes (DSPNETA) of each system and gather the following information.
a Local Network ID (LCLNETID)
b Local Control Point Name (LCLCPNAME)
1 of 3 09/10/2012 11:22
2. IBM i Support: Software Technical Document : 404791135 http://www-912.ibm.com/s_dir/SLKBase.nsf/643d2723f2907f0b862566...
Step 3: Get the IP addresses for each system.
Use CFGTCP, Option 1 to view the local interfaces and select the IP addresses you wish to use for this
connection.
Step 4: Create the APPC controller (CRTCTLAPPC).
SYSTEM A SYSTEM B
Local IP Interface Address = 1.1.1.1 Local IP Interface Address = 1.1.1.2
Local Network ID = APPN Local Network ID = APPN
Local Control Point Name = SYSTEMA Local Control Point Name = SYSTEMB
CRTCTLAPPC CRTCTLAPPC
LINKTYPE = *HPRIP LINKTYPE = *HPRIP
RMTINTNETA = 1.1.1.2 RMTINTNETA = 1.1.1.1
LCLINTNETA = 1.1.1.1 LCLINTNETA = 1.1.1.2
RMTNETID = APPN RMTNETID = APPN
RMTCPNAME = SYSTEMB RMTCPNAME = SYSTEMA
Note: At the time of this writing, a value must be specified in the LCLINTNETA other than *SYS. A virtual
APPN controller is created called QAPENDxxxx, and this is where the APPC device is attached. The original
APPC controller that is created above will be at a Varied On state and that is normal.
Step 5: The configuration object:
QAPENDxxxx controller status of ACTIVE
APPC device status of ACTIVE
Original APPC controller status of VARIED ON.
Notes:
1. The QAPENDXXXX controller will not get created until you do something to initiate an EE connection
between the two systems, like STRPASTHR.
2. If there is a NAT firewall between the two systems, the LCLINTNETA will always be an IP address that
has been configured in CFGTCP Opt 1 and the RMTINTNETA will be the public IP address of the remote,
not the private address that has been configured in CFGTCP Opt 1.
3. If this is an End Node to End Node setup with no network nodes, an APPN remote configuration list may
be necessary.
__________________________________________________________________
PMR Number:
Related APARs:
Related Public Documents:
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of
2 of 3 09/10/2012 11:22
