FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Setting Up and Operating the ePortal Specialty Engine Creating a Usercode with the GROUPCODE Attribute EPORTALCONTROLLER For a FS6200 Server, a special unprivileged usercode, called EPORTAL, with the GROUPCODE attribute of EPORTALCONTROLLER is preconfigured in the system. The EPORTALCONTROLLER attribute provides full access to the APPLIANCES share. ePortal Manager uses this usercode to obtain information about the configuration, application, and software updates from the MCP Environment. You should change the password of this usercode in both MCP Environment and ePortal environment when you setup the system for the first time. For the ePortal environment, you can change the MCP usercode/password by selecting the backend server name from the Back-End Servers page of the ePortal Manager website. In case this special usercode was removed from the MCP Environment, you can recreate this usercode by performing the step in the following example procedure. Client Access Services limits the length of this password to 14 characters. Example To create a usercode called EPORTAL with the GROUPCODE attribute EPORTALCONTROLLER, do the following on the Operations Server using the ODT in CANDE: 1. Type and transmit Run *SYSTEM/MAKEUSER. 2. Type and transmit $SET LIST IGNORE. 3. Type and transmit +USER EPORTAL; . 4. Type and transmit USER EPORTAL MINPW=1 MAXPW=1; . 5. Type and transmit USER EPORTAL PASSWORD=″″;. 6. Type and transmit USER EPORTAL GROUPCODE=EPORTALCONTROLLER;. 7. Type and transmit Bye; . Creating a Usercode with the GROUPCODE Attribute EPORTALSTUDIO Portal Developer requires a usercode with the GROUPCODE attribute or SUPPLEMENTARYGRPS attribute EPORTALSTUDIO. This usercode enables an ePortal application developer to stage applications to the MCP server APPLIANCES share. To create this usercode, do one of the following: • If the application developer usercode is not already using a GROUPCODE attribute, add EPORTALSTUDIO to the GROUPCODE attribute in the USERDATAFILE. • If the application developer usercode is already using a GROUPCODE attribute, add EPORTALSTUDIO to the SUPPLEMENTARYGRPS attribute in the USERDATAFILE. 5–2 8222 3694–000
Ensuring That the Necessary Disk Space Is Available ePortal requires the following MCP disk space: • In the APPLIANCES share: 1GB • The Client Access Services software automatically creates this share. • The ePortal installation software creates permanent directories and moves the ePortal run-time environment files to this share. ePortal Manager uses this share to obtain configuration, application, and software updates from the MCP system. Note: To relocate the MCP APPLIANCES share, see “Relocating the MCP APPLIANCES Share.” • In the INSTALLS share: 60 MB • The ePortal Developer plug-in requires disk space in this share. Relocating the MCP APPLIANCES Share The MCP APPLIANCES share contains the ePortal run-time environment files. The default family for this share is the Client Access Services family (NXSFAMILY). If you want this share in another family, use the Administration Center to specify that family in the APPLIANCES family definition. The APPLIANCES share is created in a permanent directory space. Do not move this share outside a permanent directory space. The first node of a permanent directory space always starts with *DIR. Installing ePortal Interim Corrections (ICs) To install the ePortal IC, follow the instructions in ″Installing the ePortal Interim Correction (IC)” in Section 8 of this guide. Configuring MCP Network Connection Setting Up and Operating the ePortal Specialty Engine ePortal Specialty Engine uses a private internal network connection to communicate with the MCP environment. By default, ISM-0 ePortal is configured to use 192.168.223.250 as its MCP backend server connection and ISM-1 ePortal is configured to use 192.168.224.250 as the MCP backend server connection. The following lists the default recommended TCPIP configuration setting in the MCP. • NP210 Line 3: 192.168.223.250 (ISM-0 ePortal) • NP220 Line 3: 192.168.224.250 (ISM-1 ePortal) The following lists an example of the network configuration files for MCP. 8222 3694–000 5–3
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: Section 5 Setting Up and Operating
Page 93 and 94: ; , REMOTEADDRESS = 000000000000 ,
Page 95 and 96: This command is optional. By defaul
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?