Getting Started with WebSphere Application Server

More documents

Recommendations

Info

166 Getting Started with WebSphere Application Server Community Edition JMXPort=9999 WADIClusterName=DEFAULT_WADI_CLUSTER ResourceBindingsNamePattern= RemoteDeployHostname=localhost TmId=71,84,77,73,68 DerbyPort=1527 DefaultWadiNumPartitions=24 MaxThreadPoolSize=500 ResourceBindingsNameInNamespace=jca\: OpenEJBPort=4201 ResourceBindingsQuery=?\#org.apache.geronimo.naming.ResourceSource webcontainerName=tomcat6 SMTPPort=25 FarmName=DEFAULT_FRAM HTTPSPort=8443 ActiveMQStompPort=61613 ActiveMQPort=61616 AJPPort=8009 PortOffset=0 SMTPHost=localhost ServerHostname=0.0.0.0 EndPointURI=http\://localhost\:8080 ReplicaCount=2 JMXSecurePort=9998 MinThreadPoolSize=200 Listing 9.1 - config-substitutions.properties configuration file 9.3.1 Setting the IP address and hostname The default IP address for the Community Edition server is 0.0.0.0. If you want to override this IP address, edit the file config-substitutions.properties as follows: • Change the ServerHostname attribute with the IP address of your server; for example, 9.128.237.35, or • Change the ServerHostname attribute with the host name of your server. First test your server can be accessed by using the ping command following this syntax: ping hostname. 9.3.2 Changing port numbers The easiest way to override all default port numbers is to change the PortOffset parameter into a non-zero number. In this case, the actual port number will be portnumber + PortOffset, where portnumber is the number specified in
Chapter 9 – Administering Community Edition 167 config-substitutions.properties. For example, if you review the parameter values in Listing 9.1 and change PortOffset to a value of 10, then HTTPPort will be set to 8090, and NamingPort will be set to 1109. Note: If you are running other software in your machine that uses TCP/IP ports, it is common to encounter port conflict problems when you start the Community Edition server. By changing port numbers or the PortOffset parameter, you can get past this problem. For more information, see Chapter 11, Troubleshooting. 9.3.3 Changing the username and password The default username and password for the Community Edition administrative console is system and manager respectively. You can change these defaults by editing the groups.properties and users.properties files in the /var/security directory. To add a new user and specify a password, follow these steps: 1. Open the file /var/security/groups.properties, and add a new username. For example, in Listing 9.2, another user named user1 will be created in the admin group. admin=system, user1 Listing 9.2 - groups.properties file 2. Open the file /var/security/users.properties, and add a line to specify the password for the user user1. For example, in Listing 9.3 the password has been set to password1. The username has to be the same as the one added to the groups.properties file. System=manager user1=password1 Listing 9.3 - users.properties file The Community Edition server does not save passwords as plain text in the file users.properties. Instead, it uses Advanced Encryption Standard (AES) encoded passwords after you start the server for the first time. 9.4 Introducing the administrative console The Community Edition admin console is a Web-based application user interface for managing the Community Edition server. After you start the server, you can access the admin console by pointing your browser to the URL http://localhost:8080/console. The admin console is shown in Figure 9.2 below.
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7 and 8:
Trademarks IBM, the IBM logo, and i
Page 9 and 10:
3.8 Exercises .....................
Page 11 and 12:
9.3.2 Changing port numbers .......
Page 13 and 14:
13 Preface Keeping your skills curr
Page 15:
The DB2 on Campus book series 15
Page 18 and 19:
18 Getting Started with WebSphere A
Page 21 and 22:
1 Chapter 1 - Introduction to WebSp
Page 23 and 24:
Introduction to WebSphere Applicati
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 47 and 48:
3 Chapter 3 - Development with Comm
Page 49 and 50:
Chapter 3 - Development with Commun
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
4 Chapter 4 - Working with database
Page 67 and 68:
Chapter 4 - Working with databases
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
5 Chapter 5 - Enterprise Java Beans
Page 91 and 92:
1. Define local and remote interfac
Page 93 and 94:
Chapter 5 - Enterprise Java Beans 9
Page 95 and 96:
Page 97 and 98:
Note: Chapter 5 - Enterprise Java B
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
6 Chapter 6 - Messaging Messaging i
Page 111 and 112:
Chapter 6 - Messaging 111 3. Messag
Page 113 and 114:
Chapter 6 - Messaging 113 2. Get JM
Page 115 and 116: Chapter 6 - Messaging 115 Figure 6.
Page 117 and 118: Chapter 6 - Messaging 117 Figure 6.
Page 119 and 120: Chapter 6 - Messaging 119 For examp
Page 121 and 122: textMessage.getText()); } catch (JM
Page 123 and 124: Chapter 6 - Messaging 123 3. Copy t
Page 125: Chapter 6 - Messaging 125 D. Messag
Page 128 and 129: 128 Getting Started with WebSphere
Page 161: PART III - ADMINISTERING COMMUNITY
Page 181 and 182: 10 Chapter 10 - Tuning a Community
Page 183 and 184: Chapter 10 - Tuning a Community Edi
Page 191 and 192: 10.4.2 Operating system tuning Chap
Page 193: Chapter 10 - Tuning a Community Edi
Page 211 and 212: A Appendix A - Solutions to review
Page 213 and 214: Appendix A - Solutions to review qu
Page 215 and 216: Appendix A - Solutions to review qu
Page 217 and 218:
Appendix A - Solutions to review qu
Page 219 and 220:
B Appendix B - Up and running with
Page 221 and 222:
Appendix B - Up and running with DB
Page 223 and 224:
4. The following is performed by de
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235:
C Appendix C - Using the sample cod
Page 238 and 239:
238 Getting Started with WebSphere
Page 240:
240 Getting Started with WebSphere
show all

Getting Started with WebSphere Application Server

Create successful ePaper yourself

Delete template?

Save as template?