FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Setting Up and Operating the ePortal Specialty Engine [CUCIPCM] section; ADD SERVICE EPORTALCUCI DYNAMIC = TRUE, STATIONNAME = EPORTAL/#; ENABLE SERVICE EPORTALCUCI; Validating the Connector Protocol-Specific Handler (Connector PSH) Installation and Configuration An MCP COBOL data source project accesses an MCP application by using the Connector protocol-specific handler (Connector PSH) to connect to an MCP server system. Connector PSH is installed with Transaction Server software. By default, MCP COBOL data source projects use port 7952. To verify that Connector PSH is installed and configured on the MCP Environment, enter the following command at the ODT or from a MARC window: NA CONNPSH CONFIGURE A response similar to the following indicates that the Connector PSH is installed and enabled: PSH Configuration: Current endpoint: 7952 Offers: 3 Auto logon: Enabled Clear text passwords: Enabled Close wait timeout: 60 seconds Dynamic stations: Enabled Blocked timeout: 10 minutes Dialog check interval: 5 minutes Target connections: 0 Maximum connections: 65535 If Connector PSH is installed but disabled, enter the following command at the ODT or from a MARC window to start Connector PSH: NA CONNPSH+ If Connector PSH is not installed, see the Transaction Server for ClearPath MCP Operations Guide for installation instructions. You need to modify the Connector PSH configuration using one of the following commands to enable it to work correctly with the ePortal MCP COBOL data source project: • NA CONNPSH CONFIGURE CLEARTEXTPW+ This command is required if ePortal MCP COBOL data source project uses Connect_basic option. • NA CONNPSH CONFIGURE AUTOLOGON+ This command is required if ePortal MCP COBOL data source project uses Connect_autologon option. • NA CONNPSH CONFIGURE OFFERS = 5–6 8222 3694–000
This command is optional. By default, it is set to 3. You might need to increase it to higher number if ePortal clients receive a port open error messags similar to the following: NW RESET SENT DUE TO PACKET RESEND LIMIT EXCEEDED / NW LOCAL IP ADDRESS = 192.168.223.250, LOCAL PORT = 7952) Configuring a Named Pipe ePortal includes a utility program, named SYSTEM/EPORTAL/NAMEDPIPE, that runs on the MCP Environment. This program uses the named pipe EPORTALPIPE to communicate with the ClearPath ePortal controller in order to support E-mail Notification. If the EPORTALPIPE named pipe is not already defined in the Client Access Services configuration file, define the named pipe with the attributes in the following example: SHARE EPORTALPIPE (TYPE = PIPE ,COMMENT = ″CLEARPATH EPORTAL NAMED PIPE INTERFACE″ ,ACCESS = ALL ,APPNAME = ″*SYSTEM/EPORTAL/NAMEDPIPE ON DISK″ ,APPORTINTNAME = ″EPORTALPORT″ ,PORTMAXRECSIZE = 15000 ); In the preceding example, the family name of the APPNAME attribute is DISK. You might need to modify this family name to point to the correct family on your MCP system. Configuring the MCP EMAIL Utility Setting Up and Operating the ePortal Specialty Engine The Portal Alert Notifications feature requires the MCP EMAIL utility to send an e-mail notification when an error occurs. The MCP EMAIL utility is a part of the MCP release, but is not configured by default. You need to set up the MCP EMAIL utility on the MCP and configure the Alert Notifications feature on the ePortal Specialty Engine. To configure Alert Notifications, specify the e-mail addresses to which ePortal sends the notifications. For instructions on how to configure the MCP EMAIL utility, see the System Software Utilities Operations Reference Manual. Performing Initial Configuration Tasks in ePortal Manager To complete configuration of the ePortal Specialty Engine, perform the following from the Component View tab of the MCP Console: Note: The FS6200 Server has two I/O and Specialty Engine Modules. This procedure must be performed for both the active and standby ePortal Specialty Engine running in ISM-0 and ISM-1. 8222 3694–000 5–7
Page 1 and 2:
ClearPathFS6200Server SystemImpleme
Page 3 and 4:
Contents Section 1. Introduction Ab
Page 5 and 6:
MCP Firmware Environment Policy Uti
Page 7 and 8:
Updating Specialty Engines . . . .
Page 9 and 10:
Figures 2-1. FS6200 Server Hardware
Page 11 and 12:
Tables 3-1. Physical Location of HB
Page 13 and 14:
Section 1 Introduction About This G
Page 15 and 16:
Section 2 System Overview This sect
Page 17 and 18:
• Two Processor Memory and Module
Page 19 and 20:
MCP Console s-Par Component Descrip
Page 21 and 22:
ePortal Specialty Engine The ePorta
Page 23 and 24:
Section 3 Customizing the Server Co
Page 25 and 26:
Determining Correspondence between
Page 27 and 28:
Table 3-1. Physical Location of HBA
Page 29 and 30:
• The MCP is running. • The pat
Page 31 and 32:
e. Log on to the environment. f. Cl
Page 33 and 34:
The default IP address for the intr
Page 35 and 36:
Table 3-6. Default Networking Value
Page 37 and 38:
Changing the Network Services EVLAN
Page 39 and 40:
IEEE 802.1Q VLANs allow a single ne
Page 41 and 42:
and BIP protocols. Communications b
Page 43 and 44: 4. To modify a network processor ob
Page 45 and 46: You must replace or modify the prec
Page 47 and 48: Table 3-8. MCP Networking Values fo
Page 53 and 54: Using Sample BNA Initialization Fil
Page 55 and 56: Some of the procedures in MCP Imple
Page 57 and 58: Section 4 Operating the Server This
Page 59 and 60: Powering Off the Platform Hardware
Page 61 and 62: Controlling the MCP Environment Acc
Page 63 and 64: • Domain Name System (DNS) Client
Page 65 and 66: Table 4-1. Unisys-Defined Firewall
Page 67 and 68: Table 4-2. Firewall Rules for JProc
Page 69 and 70: The utility scripts enable you to m
Page 71 and 72: Notes: Syntax Usage • Refer to th
Page 73 and 74: Sample Commands • ChangeRulesForM
Page 75 and 76: Note: The .\ notation before the sc
Page 77 and 78: Differences from Previous MCP Syste
Page 79 and 80: If you do not receive this response
Page 81 and 82: Networking Commands and Inquiries C
Page 83 and 84: • Total processor utilization rep
Page 85 and 86: I/O Time • ACQUIRE • FREE • O
Page 87 and 88: Operating the Server PING commands
Page 89 and 90: Section 5 Setting Up and Operating
Page 91 and 92: Ensuring That the Necessary Disk Sp
Page 93: ; , REMOTEADDRESS = 000000000000 ,
Page 97 and 98: 6. Perform the following actions to
Page 99 and 100: 1. From the Component View tab, exp
Page 101 and 102: Setting Up and Operating the ePorta
Page 103 and 104: Assigning ePortal Specialty Engine
Page 105 and 106: Setting Up and Operating the ePorta
Page 107 and 108: Restoring ePortal The following act
Page 109 and 110: Section 6 Setting Up and Operating
Page 111 and 112: • Microsoft Network Client This f
Page 113 and 114: Applying JProcessor Security Policy
Page 115 and 116: Section 7 Backing Up MCP Firmware C
Page 117 and 118: Section 8 Updates This section disc
Page 119 and 120: Updating MCP Firmware MCP Firmware
Page 121 and 122: Job (USERCODE) EPORTALNOTE ACCEPT:
Page 123 and 124: 17. Go back into update settings (s
Page 125 and 126: Section 9 Troubleshooting and Recov
Page 127 and 128: Accessing the Unisys Product Suppor
Page 129 and 130: Taking a Platform Firmware Livedump
Page 131 and 132: Hardware Failure Symptoms Criticali
Page 133 and 134: Workaround Use the platform managem
Page 135 and 136: • If your TCP/IP or BNA connectio
Page 137 and 138: • Obtain a Network Services firmw
Page 139 and 140: The response to the NW NP command
Page 141 and 142: Restarting a JProcessor Specialty E
Page 143 and 144: Gathering Diagnostic Information Th
Page 145 and 146:
1. Create an unprivileged MCP userc
Page 147 and 148:
The topic “I/O Configuration” i
Page 149 and 150:
cd “C:\Program Files\Unisys\MCP F
Page 151 and 152:
Restarting Platform Services Note:
Page 153 and 154:
Appendix A Building Network Initial
Page 155 and 156:
• NW TCPIP TCPIPIDENTITY NW TCPIP
Page 157 and 158:
Building Network Initialization Fil
Page 159 and 160:
Sample BNA Initialization File % On
Page 161 and 162:
Index A accessing the Unisys Suppor
Page 163 and 164:
MCP PING commands through intraplat
Page 165 and 166:
MAICP4 dump data, 9-13 Maintenance
Page 167 and 168:
elocating the MCP APPLIANCES share,
Page 170:
© 2012 Unisys Corporation. All rig
show all

FS6200 Server System Implementation Guide - Public Support ...

Create successful ePaper yourself

Delete template?

Save as template?