Port View tool to modify the port

　　Some projects require resources to take over the work of the two planes, which need a break WAS, but found it impossible to log in after the restart the console through a browser, but the portal can be accessed using normal. After a iis7 server monitoring tools of investigation, administrators feel WAS port number is fuzzy memories, to inquire about the port number, document inquiry found that even after the default port number has been modified, but I still wanted to know how to determine WAS in the system port information at this time we need to use server monitoring tool iis7 of .
　　Upon inquiry, the path:
　　there under / usr / IBM / WebSphere / AppServer / profiles / Dmgr01 / config / cells / testAPPCell01 / nodes / testAPPCellManager01 serverindex.xml a file (with the above-described path testAPPCell01 testAPPCellManager01 your own tailored to the specific environment) , there are definitions of various ports, for inquiries. for modification, you can also operate the port or modified in the console.
　　Please refer to the network port to modify the text:
　　websphere view and modify the port number
　　1, first open WAS6.0 console
　　 to admin (any identifier) user login
　　2, Open Environment -> Virtual Hosts -> default_host-> other attributes (host alias )
　　-> the first port 80 to modify other ports, and then modify the port 9080 port 80
　　3, modified (modified front to back)
　　(. 1) C: \ websphere6 \ AppServer \ Profiles \ AppSrv01 \ logs \ portdef.props
　　the 9080 port to 80
　　(2) C: \ WebSphere6 \ AppServer \ profiles \ AppSrv01 \ config \ cells \ softoaNode01Cell \ nodes \ softoaNode01 \ serverindex.xml
　　the 9080 port to 80
　　4 WAS restart the service, access the relevant application (this time without input port). Character Set can modify the jvm parameters or set environment variables before launching was
　　after deployment WAS in a small machine, set up to support Chinese character set general parameters from WORD documents directly COPY, do not know is copying errors or other reasons, led to WAS failed to start, always able to find Java Class -Dfile.encoding = GBK
　　solution: find the configuration file server1.xml modify enericJvmArguments is empty, then the normal start modifying the configuration from the management console.
　　Set parameters to support Chinese character set
　　Path: Server - application server --server1-- process defined --Java virtual machine:
　　Generic JVM arguments = -Dfile.encoding = GBK -Ddefault.client.encoding = GBK
　　modify specific configuration examples of the following file path, such as modifying the error can be modified to start WAS failed back.
　　\ usr \ IBM \ WebSphere \ AppServer \ profiles \ AppSrv01 \ config \ cells \ loushangaixNode01Cell \ nodes \ loushangaixNode01 \ servers \ server1.xml
　　file
　　genericJvmArguments="-Dfile.encoding=GBK -Ddefault.client.encoding=GBK"