As with most commercial application servers, if you plan to WebSphere Application Server (hereafter referred to as WAS) for a formal production environment or for performance testing, production test environment before testing, in addition to simple installation steps, you need to do some additional checks, planning and configuration, to ensure that your WebSphere Application Server environment safe and stable operation. Between the various versions of WebSphere Application Server installation steps not very different, WAS V6.x version than the previous version of the installation configuration steps to create profile for multi process, this example of version V6.1. WebSphere Application Server versions for the specific installation steps, refer to the WebSphere Application Server and WebSphere products were installed documentation information center, DeveloperWorks, there are many structures on the WAS environment, reference articles, such as: WAS5 installation and frequently asked questions, in WAS6. 0 ND achieve clustering, etc., see reference resources.
2. Installation preparation
Quasi-production environment in the build process, good preparation is half the recommended one by one the following pre-installation preparations.
2.1. Application Server hardware configuration
WebSphere Application Server depends on the successful implementation of a successful first target platform meets the conditions to install the software and hardware. Configuring WebSphere Application Server on the hardware requirements of the main deployment platform to be reflected in the architecture, CPU, memory and disk storage space, usually above the minimum memory requirements in the 512M, according to hardware platform, WebSphere Application Server version, the different components, requirements configuration will be slightly different, see WAS detailed system requirements. Disk space allocation please see the "2.4 to confirm whether the disk space to meet the requirements."
2.2. To confirm the operating system version meets the requirements
As a mature commercial application server, WebSphere Application Server will regularly publish different versions of WAS (eg WAS V5.0, WAS V5.1, WAS6.0 ...), components (such as: Application Server, Edge Component) Supported Operating Systems version information. WebSphere server using a supported operating system platforms, to ensure that the application server installation, use the environment during normal and stable operation. Particular attention to is that if the operating system platform, IBM WebSphere Application Server is not officially supported platform, the WebSphere application environment problems can not be obtained after the WebSphere Application Server after-sales support, let alone solve the problem.
For example, I write this, in the x86 chip, for RedHat AS 4 operating system, if you want to install WebSphere Application Server V6.1 of the Application Server component, the required operating system version is Red Hat Enterprise Linux AS, Version 4 with Update 2. If your operating system version is Red Hat Enterprise Linux AS, Version 4, you also need to install Update2, or they may experience problems.
As a supported operating system version is regularly updated, please set up WebSphere Application Server environment before the details of the light system requirements to view the current operating system version (version should be listed in exactly the same with the Internet) is required to meet the WebSphere Application Server.
2.3. To confirm the network configuration / host name to meet the requirements
WebSphere Application Server installation process, create a profile of this step requires users to fill in the machine's host name (Figure 1), and, WAS run-time also need to use the host name (Host Name). WAS host name is the physical installation of the machine's network node name, it must resolve to the server's physical network nodes. Create a profile used in the WAS host name value can be fully qualified DNS host name (for example: hosta.cn.ibm.com), short host name (for example: hosta), or even a digital IP address (example: 192.168. 1.3), but it must be the actual configuration of WAS where the server host name. And, when put into use after the completion of WAS configuration is not recommended to change the host name you set, even if changed, the process is also complicated. Therefore, based on actual experience, we recommend users to install WebSphere Application Server configuration before the host name. If you use the fully qualified DNS host name or the short host name, you can view the current system hostname command to the hostname.If not configured, then the hosts file to add the appropriate entries.
Figure 1. Create a profile enter the host name when
FAQ 1: After installing WAS, change the host name, WAS not start or stop, log error: javax.naming.ConfigurationException: Cannot get canonical host name for server.Therefore, a summary document created before the WAS, according to the actual situation, choose one of three forms of host name (fully qualified DNS host name, short host name or numeric IP address) in the host name remains the same kind of form, as WAS Use the host name, the profile creation wizard (Figure 1) fill. If you are using DHCP or if you frequently change the IP address, then we recommend in the summary file was created using the fully qualified DNS host name or the short host name; If the machine ip fixed, while the fully qualified DNS host name or the short host name may change profile created in the use of digital ip.
FAQ 2: If you need to create a cluster, make sure the network configuration, in addition to ensure that the machine host name is configured correctly, it must also ensure that the cluster where the machines can ping each other through the host name.Otherwise, add node cluster created in step might not succeed.
2.4. To confirm whether the disk space to meet the requirements
Consider the allocation of hard disk space, in UNIX or Linux platform can use df-k first see the directory size.If it is installed in a production environment WebSphere Application Server, the general calculated from the following aspects to reserve space.
This space is generally about 1G, different system platforms in a slightly different. WAS installed directory should be reserved this space. WebSphere Application Server on Linux, the default installation path is / opt / IBM / WebSphere / AppServer, under the AIX default installation path is / usr / IBM / WebSphere / AppServer (later referred to as the path we WAS_HOME).Users can modify the installation when installing WAS path.
WebSphere Application Server V6.1 to create a profile with three kinds of basic types, each profile the space below: Application Server (Application Server): In the WebSphere Application Server installation did not choose to install the sample program, this profile occupied disk space of about 200M; Deployment Manager: 30M; custom profile (Custom, or node agent): 10M.
If you want to install the WEB server, the server is located in the WEB server, WEB server to allow the share of disk space. IBM HTTP Server general occupy the space around 110M.
If you installed the WEB server, WEB server is located in the machine normally will install the Web Server Plug-in component, the component share of disk space is about 200M.
WebSphere Application Server system log space. Estimates of log space to integrate the system configuration of the log.WebSphere Application Server logs are the main SystemOut.log, SystemErr.log.We can set the log file size and preserve the history of the number of log files, which can estimate their needs space. Please refer to "the necessary adjustment of parameters" section to learn how to adjust parameters of WebSphere Application Server logs.
If you have WEB server, WEB server logs need to consider space.If a customer opens a WEB server access log access.log (enabled by default), fast growth of this log, to allow enough space.
backup files needed space. WebSphere Application Server provides a backup command (backupConfig.bat / sh), used to back up the application server's configuration and the applications. For a typical production system, WebSphere Application Server configuration file often more than 100M. BackupConfig command is issued, the use-logfile parameter to specify a location for the backup file.
When the system error log, for example, JVM OutOfMemory occurs when the majority of platforms in the WebSphere Application Server will default to write papers and heapdump javacore documents, records the error occurs when the JVM Heap, threads, so as to prepare error diagnostic use.Although the application server parameters can be adjusted so that does not produce such documents, but in order to analyze problems, usually starting from such documents. Such documents are usually particularly large, such as heapdump file, may reach hundreds of M.If the repeated occurrence of OutOfMemroy, occupied disk space quickly. Therefore, we must consider the disk space reserved for such documents.
WAS installation program also requires the system's temporary directory / tmp has more than 100M free space.
Users to publish to the WebSphere Application Server on all application and the application of its own application log space.Associated with the practical application of this size, and different applications can vary widely.
To understand the different platform specific disk space requirements, refer to the WAS V6.1 Information Center, "prepared for the product to install the operating system" section of the content.
2.5. For a specific operating system configuration
WebSphere Application Server mentioned earlier operating system versions to support specific requirements, in addition, WAS Information Center, also on a specific operating system version of the installed packages, kernel parameters, there are special requirements. For example, RHEL AS4, the information center instructions to install the compat-libstdc + +-33-3.2.3-47.3.ppc.rpm package (this is to maintain compatibility with C + + run-time necessary for such GSKit components, Java 2 Software Development Kit (SDK) and Web server plug-in use) and some other packages. For Linux, Solaris, HP and other systems, also need to adjust some kernel parameters accordingly. Please refer to WAS V6.1 Information Center, "prepared for the product to install the operating system" section of the content. For Solaris systems, need to adjust the parameter list are listed below:
set shmsys:shminfo_shmmax = 4294967295
set shmsys:shminfo_shmseg = 1024
set shmsys:shminfo_shmmni = 1024
set semsys:seminfo_semaem = 16384
set semsys:seminfo_semmni = 1024
set semsys:seminfo_semmap = 1026
set semsys:seminfo_semmns = 16384
set semsys:seminfo_semmsl = 100
set semsys:seminfo_semopm = 100
set semsys:seminfo_semmnu = 2048
set semsys:seminfo_semume = 256
set msgsys:msginfo_msgmap = 1026
set msgsys:msginfo_msgmax = 65535
set rlim_fd_cur=1024 set rlim_fd_cur = 1024
2.6. For Linux / Unix systems, to confirm to start the graphical interface
WAS installation can use the man-machine interactive graphical interface to install or batch installation (known as the silent installation, silent installation, pre-written response file, start the installation process does not require a graphical interface or human-computer interaction). If you use the graphical interface installed on the server is a Linux / UNIX platforms, we often do not have opportunities to directly use the server's screen / console, but through their own machine telenet to the server up. This direct telnet command line mode, start the graphical interface may not support the need to use Xmanager, X-Win32 X Window tools and other support software. If the graphics shown in Figure 2 shows that the terminal you can start your graphical interface.
Figure 2. Verify to start the graphical interface
2.7. Ready to install the appropriate media
WAS is a cross-platform product, different UNIX, Linux, Windows platform, 32-bit or 64-bit operating systems, the installation media is not the same, and the product contains the Application Server, Web Server, Edge Component and many other groups cases, when set up WebSphere environment, you need to order the WAS product package (including all platforms, components, multiple CD) in the Select the installation media.Therefore, we need to install before installing the WAS components, operating system version, operating system, the median, select the desired media.For example, if we are to x86 architecture, 64-bit (note, here is the 64-bit operating system is 64-bit) and Linux AS 4 install WAS, it should select the WebSphere Application Server for x86 64-bit Linux installation media ; if we are to install IBM Http Server or update installer, the two components are in the WebSphere Application Server Supplements CD in the same manner, according to the operating system version, the median, server chips, we can select the required media the. If you need to patch WAS installation is recommended before installing the WAS prepared ahead of time to download the patch to use during installation. Details in the "patch" a detail.
2.8. 2.8. Design WebSphere environment, the topology structure
Different scenarios depending on the application, we need to decide WAS, Web server, which were installed on the server, if the need to configure the cluster environment, also need to consider the Deployment Manager, all members of the cluster nodes and segments in which the server. For example, if we want to configure a cluster environment, the installation, we will usually design shown in Figure 3, a topology map to determine the actual installation on each server to install, configure components. For example, as shown in Figure 3, the figure solid line is the run time of the request flow, dashed line is the WAS control flow between the various components.We can see the machine in the hosta, WAS components should be installed, and create a Deployment Manager, NodeA profile, configure the cluster members of the C1 and C2; in hostb machines should be installed on WAS components, create NodeB profile, configure the cluster member of C3 and C4.In machine3 machine should be installed on IBM Http Server and Plug-in component. Where, WAS cluster configuration is very convenient, you can create a complete profile after the flexibility to adjust.
Figure 3. Topology architecture design WAS
2.9. Other common precautions
Some other common considerations include competence, port control and so on. For example:
WebSphere Application Server in Unix / Linux systems to support non-root user and root user.But for the sake of simplicity of operation set, they usually carried out under the root user.
Some production systems with limited access to the port, or the system may have occupied WAS will use the default port, therefore, need to change the WAS to use the port (this task will "change the port used by WAS" in detail) and so on .
If necessary create a cluster, be sure to participate in Cell environment between the time the same machine, same time zone, the proposed error control in the second level. Otherwise, the add node process may not succeed.
3. Install WebSphere Application Server
WAS installation process is very simple, usually divided into three steps: Install the WAS product, for product patches (if any patches), to create profile.If your environment is very clean, no special restrictions on the installation process most of the time is to click the default "Next". Of course, according to the different environment, usually to note the following:
3.1. Installation Notes WAS products
WAS to use graphical interface install process is very simple, usually do not need to make specific changes. Here are some common installation notes and tips to improve the speed of installation:
Typically, if your system has been installed WAS products, before installing WAS Product suggested turning off the WAS process is running. If you installed the IBM Http Server, is usually best stopped running Apache Http Server or other IBM Http Server process. In the Unix / Linux system, you can use ps-ef | grep java command to see if there was the process of the current system, with ps-ef | grep httpd command to view the current system is a http server process running.
Install WAS can perform launchpad.bat / luanchpad.exe, start the "start panel" from the start panel, click "Start WebSphere Application Server installation wizard. If you can not successfully start "start panel", directly to the installation media directory of the WAS directory, the implementation of install.exe / install.sh can.
Garbled: Launchpad or installation wizard displays WAS language and the local operating system language settings. If the local operating system language set to English, the WAS installation wizard will appear in Chinese. If you find that the wizard is displayed as garbled language, you can first local operating system language set to English, using English language to install WAS. This installed the WAS still have Chinese support, do not worry. export LANG=en_US In the Unix / Linux platforms, change the language to English using the following command: export LANG = en_US
WAS installation process may choose whether to install the sample application (samples), to the development environment and production environment, access to higher performance, do not install the samples. By omitting the sample, you can start the application server and save 60% time 15% of disk space; can save a considerable degree of process usage; and you can save each WAS product installation and application server profile creation time.
A running environment must contain at least one WAS profile. Therefore, WAS product installation process gives users the option to create the initial profile. If you installed the patch even after the WAS product, first proposed at this time do not choose to create any initial profile (Fig. 4), to save the time required for patching. If the profile was not created during installation, the installation will be displayed after the end of WAS products used to start the "create profile" wizard option.For the same reason, if you need to patch, and we will create a profile into the job after patching, so do not select the start here, "create profile" wizard.
Figure 4. Install file do not choose to create an initial outline
If you are using WAS version has been put on the market for some time, based on user testing and use, WAS will regularly publish patch (Fix Pack) or patches (Fix).Recommend that you install the patch in a test environment, ensure that the installation of the patch will not run on your negative impact on the environment, then install the patch to the production environment. Once you've gone through proper testing, take the initiative to install the patch to prevent, to avoid some may cause problems on your system fail. WAS V6.x patch upgrade patch upgrade strategy to understand details of the strategies. IBM support site and can download WAS WAS patch download patch.
In general, WAS patch naming specification: Version name - Product names - Product Component name - platform name - patch ID name. Pak. For example ,6.1.0-WS-WAS-SolarisSparc64-FP0000007. Pak, this is the WAS WAS V6.1 operating system components for the Solaris Sparc64 FP0000007 patch. If you install WAS, need product components and WAS named WASSDK patch; If you installed the IBM Http Server, IHS needs to product components called patches; if you need to install the product components Plugin patch called PLG . Typically, the same patch number of patches, first install WASSDK patch, then install WAS patch. After every patch of the process are:
1) copy the patch file to patch the installation directory of the maintenance facility directory;
2) plant in the patch installation directory, do the. / Update.sh command starts patch factory;
3) In the "installation directory" in the components chosen to Yaoda patch installation directory. Typically, on the WAS component patches installed automatically identify the location; for IBM Http Server (referred to as IHS) or Plug-in such components, need to select the correct installation position;
4) maintenance package selection page, select the patch you want to play.
3.3. Create a profile
Profile is used to define a set of run-time environment in which each profile is a group completely separate from the runtime environment. We mentioned earlier, there are three basic types of profile. Create a profile in the process, usually we have to understand the following details:
There are two ways to create a profile, create a graphical wizard and command line. Simple and intuitive to operate, we usually create a graphical wizard (Executive WAS_Home / bin / ProfileManagement / pmt.sh start the wizard).If you are installing 64-bit WAS, there is no tool for the graphical creation wizard. At this time, please use the. / Manageprofiles.sh command. export WAS_HOME=/opt/IBM/WebSphere/AppServer For example: In the UNIX platform to create an Application Server called AppSrv01 type of profile, use the following operation manageprofiles command: export WAS_HOME = / opt / IBM / WebSphere / AppServer
cd $ WAS_HOME / bin
/ Manageprofiles.sh-create-profileName AppSrv01
-ProfilePath $ WAS_HOME/profiles/AppSrv01
-TemplatePath $ WAS_HOME / profileTemplates / default
-HostName kcgg1d7.itso.ibm.com-enableAdminSecurity true
-AdminUserName adminUser_ID-adminPassword adminPassword
Note that the command and parameters case sensitive.Manageprofiles command parameter syntax and more options, see the Redbook sg247304.pdf or information center.
In the "Confirm network configuration / host name to meet the requirements" section, referred to select the appropriate host name; create a profile (Figure 1) process, the majority of cases, the wizard automatically identifies the host name to meet the requirements, otherwise We need to fill in the wizard to profile an appropriate host name. In the same machine with the profile creation wizard to create multiple profile, the automatic recognition of host name may be added fully qualified domain name such as hosta.cn.ibm.com, it may be a short name of hosta. Both forms of support, but not in a cell (Cell refers to multiple instances of WAS consisting of a managed domain) name in the mix these two methods.
Create an application server profile process, you can apply to be selected to create the development environment or production environment using the application server instance. For example, development environment, developers can choose to use the template to create a server, developed the template for development purposes optimized configuration, reducing the WAS start time and allow the server to the function of less hardware to run.However, in a production environment, do not select "Use Development template.
profile creation process, we can select "Enable management of safety," so the user during log management console, stop the WAS instance and other management tasks need to enter user name / password. Note that if you create the profile in the process of managing security is not enabled, or enable the management of security after the wish to modify the user name or password, can create the profile again after completion of modification (see "Managing Security").
Process can create a profile view / change the profile share of port.
Figure 5 shows the creation of this profile instance startup will take up the port, we can see the management console port is 9060, Http transfer port (that is, applications access to the port) is 9080.If you use the command line, create a profile wizard, not through the graphical display to see these ports, if you want to see the port, you can create a profile view profile obtained after the port values (see the "View / change the application server port"); If you want to modify these ports, you can create a profile using parameter-portsFile or-startingPort specified port. Of course, all these port values can be created in the profile changes again after completion.
Figure 5. Create a profile to display port
4. Necessary to adjust parameters
WAS installed in a production environment and create a complete summary of available files, the actual situation must be necessary to adjust parameters in order to improve WAS performance, easy error diagnosis.These parameters are usually combined with running the actual situation of the environment, the actual amount of concurrency and server resource utilization to adjust. Complete tuning involves operating system, application, application server and database integrated adjustment of specific parameters to be adjusted, meaning, see the resources mentioned in WAS resource monitoring and performance tuning section, for example, 17.5 sections Redbook sg246392 clear about the performance tuning usually involves adjusting the parameters and principles. In this paper, only the application server itself for a number of important parameters to adjust the guiding principles and lessons of experience, so that readers can quickly start:
Java Virtual Machine heap size (JVM Heap Size): control the JVM heap size of the code can use the unit M. The parameters of the server -> Application Server> Process Definition> Java Virtual Machine set. JVM maximum heap size of the default is 256M, in a production environment is usually the situation according to the machine physical memory, applications to set the operating characteristics, and most cases have to adjust this parameter large.Experience, memory is sufficient, the adjustment is usually between the 500M to 1024M. Note that the proposed maximum JVM Heap no more than 1024M, if the JVM Heap Size too large may lead to memory paging, or cause JVM garbage collection time is too long, but affect the application server performance.Tuning the Java virtual machine specific information, refer to the JVM parameters to adjust.
Web container thread pool: This parameter in the "Server> Application Server> server1> thread pool" and "WebContainer" in the set (Figure 6), the default value is 10 to 50. If the hardware resources allow, usually the maximum size of the thread pool transferred to 100.
Figure 6. Adjust the thread pool
Data source connection pool: the parameter in the resource -> JDBC-> Data Source -> data source name, select the "Connection Pool Settings" is set, the default size is 1 to 10. Queue based on the resource set (Queue) principle, from the Web container thread pool, to the data source connection pool parameter setting, should be both large and small pipe. We list the Web container in front of the thread pool's maximum setting of 100, for the data source connection pooling, set the maximum usually does not exceed 50. In most cases adjusted to 30.Actual operation can modify the value of this parameter to observe whether adjustments have a positive impact on performance. Note that if the maximum size of the database connection pool transfer too large, JVM limited resources are spent in maintaining the connection pool to handle the database connection, we may cause performance degradation WAS.
WAS process, the log parameters: WAS process logs are most commonly used SystemOut.log and SystemErr.log.The two log default size 1M, history, log file number 1.In a production environment, this setting is usually not sufficient to fully save an error message when a problem occurs.We can modify the default log size, the number of historical log files to store more information. Be careful not to single copies of the log file size is set too large (for example, more than 10M), or may affect the WAS performance.In addition, we propose to apply the log and the log points from WAS.If the application of large amounts of System.out.print or System.err.print to save the application state logs, may also affect server performance.
Figure 7. Modify the WAS log properties
Heapdump file: earlier we mentioned, Heapdump file on the disk space occupied by very quickly, so you can set parameters to Heapdump file IBM_HEAPDUMP stored in the specified directory.
Web server access logs access.log: IBM Http Server's access log access.log by default is turned on, which records the requests for information through the Http server. In highly concurrent systems, the log growth is over, when the log is too large, it may take up too much disk space or cause performance degradation, if your system does not need the logs, or other technical means to save the user access to information may close the log.Specifically: on IBM Http Server installation directory / conf directory under the httpd.conf file, search CustomLog, the with the # comment out the CustomLog line where you can.
5. Frequently daily management tasks
As the access control needs of the production environment, set up after the WebSphere environment, usually may be required to modify the application of access ports, or change the WAS administrator password, enable / disable management of security and so on.
5.1. View / Change application server ports
Application Server installation has finished, the production environment in order to avoid port conflicts, port access control, sometimes we need to view or change application server ports.
View port change application access ports by default, WAS administration console and application access are two different ports. Access Management Console or WAS WAS deployed applications, the port used by the application server and virtual host port decision. Suppose we want applications to access the port from 9080 into 9082 (the actual work, if there is no Web server, and some environmental applications will want to visit the port into a 80, a similar method), according to the following steps: Log Management Control WAS station, select the left menu Server - Application Server, click server1, select the "port", click "WC_defaulthost" (Figure 8), modify the port to any port you want (careful to avoid port conflicts), for example, 9082. Then click "OK. And then "Save."
Figure 8. Modify application access port
Then, select the menu on the left of the environment - a virtual host, click the "default_host", select the "Host Alias" (Figure 9), the original port 9080 change the previous application server / port / WC_defaulthost the same port, for example, 9082. Or click "New", the following changes in WC_defaulthost enter the port number, click "OK", "Save."
Figure 9. Modify the virtual host
Of course, if you are in front of application server / port / WC_defaulthost set the port has been in virtual host / default_host / host alias list, you do not need to do changes or new host alias port work. Was to ensure that the application server / port / WC_defaulthost port in virtual host / default_host host alias list. Changes take effect after restarting the WAS server.
WAS administrative console to change the port landing WAS Admin Console, select the left menu Server - Application Server, click server1 select "port. Then change the WC_adminhost hope for their own management console port.Then click "OK", "Save.Select the left menu environment - a virtual host, click on; and choose admin_host, select the "Host Alias.Into the original port 9060 and the previous application server / port / WC_adminhost same port, for example, 9063. Or click "New" to create a host alias, * 9063. And then "OK", "Save. Was to ensure that the application server / port / WC_adminhost port in virtual host / admin_host host alias list.
5.2. Management of security
Environmental requirements for the production of variability, the actual structures in the WAS environment, security may be involved in a variety of operations management.
Enable the management of security will be activated to enable management security to prevent unauthorized users from using the server's settings, simply, into the management console, change the application server configuration, stop the application server process, these management tasks are required to enter pre-defined user name and password to complete. By default, create a profile will enable the management of safety (Figure 9).If you did not create a profile select "Enable management of security", in the subsequent process of using it want to enable, you can by following these steps:
First into the console, for example: [url] http://was_ip:9060/admin [/ url], Note that it must be a logged in user to set the security of users.For example, admin. Select "Security"> "security management, application and infrastructure", then click on the "Security Configuration Wizard" (Figure 10).For configuration simplicity, in the "Specify the scope of protection", you can not choose the "Use Java 2 security to restrict application access to local resources"; in the "Select user repository" in the accept the default option, the user repository for the " Joint repository ", click" Next "; in the configuration repository, fill in the user user name, password. If you are a first time enable the management of security, enter a new user name (your login management console user name) and password. This user name password is arbitrary, does not require the operating system user, because the joint repository entries from the default user file; if previously enabled through the use of the repository management of security, the use of the repository holding management Members of privileged user name and password. Click "Next", "complete. Save the application server after the restart, then login management console, etc. need to provide your pre-defined user name / password.
Figure 10. Configuration management security
Disable disable management of security management console is simple, as shown in Figure 10, page, do not select "Enable Management Security", click the "Apply" to save and restart the application server. There is a special case, special, such as forgotten administrator password, this time we are unable to access management console, which can not be disabled in the management console management of security. At this time, from $ WAS_HOME / profiles / xxx Summary of the file name / bin directory, issue the following command: wsadmin-conntype NONE. When the wsadmin command line window appears, issue the following command: securityoff.
Figure 11. Manage Users
Forget administrator password if you forget the administrator password, we can not enter the management console to change the password. At this point, need to use the "Disable Security Management" section of the method wsadmin command to disable management of security, then "change the administrator password", once again, "enable the management of security" can be.
Management to create more user-management-enabled WAS security environment, there is only one default administrator ID, which means the same time only one person can log management console. This is more than the development team released the same WAS test environment is not easy. You can start to create a repository user, and then assign the user ID corresponding management role. Concrete steps are as follows: 1) Select the "Users and Groups"> "Manage Users", shown in Figure 24, click on "Add" to add a user ID, for example, admin1. Save. Save. 2) Select "Users and Groups"> "Manage User roles", shown in Figure 25, enter the user name (must be in the repository user name already exists), select the appropriate administrative role, for example, "Administrator . " Click "OK" to save. In this way, the next restart WAS, two users can simultaneously log management console.
Figure 12. Manage user roles
5.3. Backup / restore profile
Production environment, profile configuration is too complicated or frequently change, we need to regularly back up the profile in order to quickly recover when necessary. You can use the backup configuration file backupConfig command. For example, to back up the current configuration profile AppSrv01 available from $ WAS_HOME/profiles/AppSrv01/bin directory, issue the command backupConfig, it will AppSrv01 current default profile to generate a compressed package, you can also specify the name of the archive For example: backupConfig WebSphereConfig_2007_05_30.zip. Recovery configuration, use restoreConfig WebSphereConfig_2007_05_30.zip.
5.4. The right to uninstall WAS
Need to be reminded, WAS the uninstall process is not directly delete the directory, if you do, next time you may not be in the same machine successfully installed WAS. WAS uninstalling before the WAS process stop the machine, using ps-ef | grep java to ensure that no process was running. Then, the implementation of WAS_HOME / uninstall / uninstall.sh command to uninstall WAS. If for some special reason to uninstall wizard to guide the uninstall process is not successful (for example, you simply delete the WAS installation directory), or in the same directory you want to install WAS, please refer to the information center "manual uninstall" the advice given.
6. Application deployment
Application deployment usually involves several tasks as follows: Configure application environment required: such as the system variables, virtual host, class path, security, etc.; configure the resources needed for applications such as JMS resources, data sources and so on. One needs to note:
Application Package: Application deployed on WebSphere Application Server can be packaged *. ear / *. war file, it can be packaged, but not the components meet the J2EE specifications. In a production environment is recommended to use packaged *. ear / *. war file for easy version control and management. For complex projects, multiple J2EE components of the package, see the article "package on the J2EE application development project management."
Management Utility Jar pack: Most J2EE applications have some common Utility Jar package, first of all to emphasize is this: we must avoid in the same class load path exists multiple versions of the same class! In operation, this will bring a lot of strange and difficult to diagnose the problem. Second, the JDBC driver for a higher level of such common Utility Jar package, can be placed in
Jar package conflicts: Jar package conflicts in large-scale Java software development frequently encountered, simply, when different applications use the public Utility Jar package, application server exists in the bottom of the Jar package the same name, and version of the different classes, we Jar package called the conflict. This solution to the problem can refer to the article on how to resolve Jar package in WebSphere in the conflict.
Session Timeout: scenarios for the different expectations of different applications different session timeout. WebSphere Application Server session management into Application server, Application, Web Module three levels. As the name suggests, in each particular level change of the session management configuration, the current level of play. Deployed in WebSphere Application Server on the application, the default session timeout is 30 minutes, the default session management level is the Application Server. If you expect to change your application, for example, DefaultApplication session timeout, may proceed as follows: Select the application> Application Name> session management (Figure 13), select "Overwrite Session Management", and "super-set time "in time to fill in the desired session timeout. Click "OK" to save the can.
Figure 13. Session Management
When writing Java applications need to configure environment variables when some variables can be used in the application server startup script-D parameter specified in the application server can also> application server name (for example, server1)> Process Definition> Java Virtual machine settings "General JVM parameter"-Daaa = xxx.
When a problem in the WAS environment, the most convenient is to use online resources to access relevant information. This article has too much respect, in order to achieve this goal: "to try to complete the primary users a quick start guide", I had an old tune here, please refer to where to learn WebSphere? Common understanding of WebSphere Application Server Online resources.
Understand the WAS process is gradual, and I hope this article can be installed in WAS sample documents and user's WebSphere production environment set up to provide a transition between the practice, save you time. From the engineer's point of view, a problem not a bad thing, a problem the more experience the more access to information, and through a variety of sources of technical support for IBM, I believe your experience using the WAS will be more beautiful