text:
Soft - is your software and documentation
Ø Logon – without logon window, auto, etc...
Ø CM Server – utilities, etc....
Ø Environment -
Ø Perl Hooks – understanding with CQWeb, etc...
The ClearQuest web "How do I" covers: (Last updated 9-Oct-09)
1. How do I – understand the users getting restricted access in ClearQuest Web on Linux/UNIX platforms issue
2. How do I – understand why the Database connections are missing in ClearQuest Web 7.1 login screen
3. How do I - log on to the ClearQuest Web server without the login window
4. How do I - force an SSL connection with Change Management Server (CM Server) for ClearQuest Web
5. How do I – understand the Rational Change Management (CM) Server Administration utility - new in 184.108.40.206
6. How do I – understand why ClearQuest Web WAS Service errors upon stop/restart
7. How do I – understand why there is no response when trying to create a query on ClearQuest Web
8. How do I – understand the MustGather: ClearQuest Web 7.1 Server
9. How do I - configure ClearQuest Web 7.1.x to use an alternate HTTP port
10. How do I – understand the Change Management (CM) Server configuration guidelines for ClearQuest Web
11. How do I – understand why the ClearQuest Web Server requires a CM Server
12. How do I – understand the configuring of ClearQuest Web 7.0.x to use an alternate HTTP port
13. How do I – do CQWeb: Performance and Tuning
14. How do I - run reports when using the ClearQuest Web client
15. How do I – understand using CTRL-A within a text box causes entire page to highlight in ClearQuest Web
16. How do I – understand the CM Server configuration guidelines for ClearQuest Web in ClearQuest version 7.1
17. How do I – understand why the calendar selects the wrong month in Web client
18. How do I – understand the Incorrect date and time formatting on Web client
19. How do I - run Charts and Reports UNIX with ClearQuest Web
20. How do I - use a custom homepage with ClearQuest Web 7.1
21. How do I - access a Test Database in ClearQuest Web 7.1
22. How do I - access a test database from the ClearQuest Web ASP client
23. How do I – access a test database from the ClearQuest Web Java client
24. How do I - configure CQWeb Web Server to redirect to RWP
25. How do I - set up the cqweb_autologin for use with the ClearCase Remote Client and ClearQuest Integration
26. How do I – understand the could not wsithc database error within ClearQuest Web
27. How do I – understand the further details regarding the configuration of MAPI on E-Mail notification for ClearQuest Web
28. How do I – understand the calling system() from perl hooks under CQWeb is unreliable on perhaps all platforms issue
This technote explains a resolution for users getting restricted access errors when attempting to access an IBM® Rational® ClearQuest® Web server on a Linux® or UNIX® platform, even though licenses are available.
The ClearQuest Request Manager is not able to get the license server information. The native client on the server can login without any problems, but when accessing the web server, they get restricted access even though there are licenses available and restricted access is not enabled.
Resolving the problem
To resolve this situation, check the following settings on the ClearQuest server:
1. Go to the <CQ_HOME>/bin/clearquest file.
2. Look for line that says cq_license=port@host. It should be in the format port@host even when the port is default( e.g. 27000@xyz). Change this parameter if necessary.
3. Restart the Request Manager using the <CQ_HOME>/cqweb/cqserver_startup script. By default CQ_HOME is /opt/rational/clearquest.
4. If the previous
steps do not work, you can set up the environment variable LM_LICENSE_FILE
in the <CQ_HOME>/cqweb/cqserver/start_cqrm.sh file in 2003 versions and <CQ_HOME>/cqweb/cqregsvr/start_cqreg.sh file in 7.0.* and higher versions as follows:
Restart Request Manager as stated above.
Users can access the login screen for ClearQuest Web 7.1, but the pull-down menu with schema repository connections is blank. This prevents users from logging into ClearQuest through the web client; local client software can view the available connections without a problem.
This problem might occur if the operating system does not have enough memory to effectively run the CM Server process
Diagnosing the problem
Check the CM Server SystemOut.log file for error messages indicating a memory problem. The log file is located in the following directories, by default:
UNIX or Linux
In the file, search for the following, possible error message regarding memory:
Unable to start server: cqrpc.sh: java.io.IOException: Cannot allocate memory
Resolving the problem
Should the CM Server logs contain the error message referencing memory allocation problems, review these items:
The URL format for automatically logging into ClearQuest has changed in different versions. Refer to the following table for the ClearQuest Web server versions 2003.06.13 and later:
ClearQuest Web server name
Your ClearQuest schema repository connection name
Logical Database Name of your target ClearQuest database
ClearQuest user name
ClearQuest password
ClearQuest versions 7.0, 2003.06.14 - 2003.06.16
For example if you have the following URL
that works in ClearQuest Web 2003.06.14 and later:
ClearQuest versions 2003.06.13
For example if you have the following URL that works in ClearQuest Web 2003.06.13. This syntax was changed in later versions of ClearQuest.
ClearQuest versions 2003.06.12 and earlier
Type in the address mentioned below, in your Browser, specifying your target the database in ClearQuest Web.
To create a URL that will allow you to
login to your ClearQuest database on a ClearQuest Web Server, use the following
URL syntax, substituting you values for this example:
http://web_server_name/clearquest_virtual_directory/logon/default.asp? DbSetName=2003.06.00&DatabaseName=SAMPL&user=admin&password=pwd
For example:
http://localhost/CQWeb/logon/default.asp? DbSetName=2003.06.00&DatabaseName=SAMPL&user=admin&password=""
Windows server name
ClearQuest virtual directory in IIS. Typically "CQWeb" by default
Your ClearQuest schema repository connection name
Logical Database Name of your target ClearQuest database
ClearQuest user name
ClearQuest password
How do I force an SSL connection with Change Management Server (CM Server) for ClearQuest Web??
There is incorrect path specifications and incomplete information in the ClearCase and ClearQuest 7.1 and 126.96.36.199 help and Information Centers on how to force an SSL connection with Change Management Server for ClearQuest Web.
Forcing an SSL
connection with CM Server for ClearQuest Web
You can force the Change Management Server (CM Server) to process non-SSL requests as SSL requests.
The following variables are used in path names in this topic:
CM Server host name
Directory where the Rational common files are installed
To force CM Server
to process non-SSL requests as SSL requests:
1. Edit the file httpd.conf, which is located in the following directory:
a. Add or modify the VirtualHost settings to include the following commands. Replace yourServerName with the name of your CM Server host, and %RATIONAL_COMMON% or $RATIONAL_COMMON with the path specification where the Rational common files are installed:
<VirtualHost *:80>
ServerName yourServerName
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*)$ https://yourServerName$1 [R]
RewriteLogLevel 0
RewriteLog "drive:\%RATIONAL_COMMON%\IHS\logs\rewrite.log"
<VirtualHost *:80>
ServerName yourServerName
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*)$ https://yourServerName$1 [R]
RewriteLogLevel 0
RewriteLog "$RATIONAL_COMMON/IHS/logs/rewrite.log"
Attention: Ensure that the commands are placed appropriately in the file so that they run before the WebSphere® Application module and the WebSphere Plug-in module.
b. Include the file ssl.conf by adding the following command:
# include ssl information
Include conf/ssl.conf
c. Save your changes and close the file.
2. Edit the file ssl.conf to provide the correct SSL certificate path information. The file ssl.conf is located in the following directory:
Save your changes and close the file.
3. Edit the file cqServerConn.properties, which resides in the following directory:
a. Change the value
of the parameter HELP_SERVER_URL from this:
to this:
b. Save your changes and close the file.
4. Restart the IBM HTTP Server.
This technical note describes the capabilities of the Rational Change Management (CM) Server Administration utility, introduced in ClearCase and ClearQuest version 22.214.171.124 as part of the Web support installation option.
The CM Server Administration utility is automatically deployed to the same WebSphere Application Server instance that hosts the CM Server.
You can manually deploy the CM Server Administration utility to another WebSphere Application Server instance. The file TeamAdminWebEAR.ear, which includes the CM Server Administration utility, is installed in the directory $RATIONAL_COMMON\CM\lib.
Getting started
The CM Server Administration utility is a browser-based interface that lets you monitor and configure a single CM Server system.
To start the utility:
1. Enter the following URL in a supported
browser window (Microsoft Internet Explorer 6.0 or later, or Firefox 2.0 or
http://<cm-server-name>/TeamAdminWeb (if you are using IBM HTTP Server)
2. At the log in prompt, enter the following information:
3. Click Connect.
Overall monitoring
Summary information since the last time the CM Server host was started appears in a table.
Monitoring CM Server activity
There are two main monitoring views, each available on a separate tab:
Configuring and controlling the CM Server
To configure and control the CM Server, open the Site Configuration dialog box by clicking Site Administration > Configuration on the toolbar.
Each tab in the Site Configuration dialog box represents a CM Server MBean that controls configuration data:
All changes in the Site Configuration dialog box are made in real time. You do not need to restart the CM Server system. Note that some attributes on the CM Server ClearCase Options tab and the CM Server ClearQuest Options tab affect only new backend RPC server processes.
1. If the CM Server host has only the ClearCase or ClearQuest component installed, the configuration options for the product that is not installed still appear.
Setting some attributes to values that are outside the attribute range may not appear as errors until you refresh the Site Configuration dialog box.
This technote provides steps for troubleshooting IBM® Rational® ClearQuest® Web Service errors when stopping or restarting the service
ClearQuest Web Websphere Application Server V6 - RWP Servlet Service Errors
WAS Server Logs:
Every application
server process gets several log files:
<profile>/logs/<server_name>/ SystemErr.log
Where <profile> is
<embexpress_install>/profiles/profile1 (Unix and Windows – CQ Web; Windows only- PjC) On Windows we also install profile2 (for ReqWeb).
<server_name> is server1 for RWP configuration.
Diagnosing the problem
Issues with WAS
Service Stop/Start Errors:
Stop error
If this happens, check that the IBM HTTP Server Service is stopped first. It must be stopped for a WAS Stop and started before a WAS Start.
Start error
Is the WASServer.exe process actually running, even after you stop it? Look in the task manager and kill the process and then do a "WAS - Stop" and then a "WAS Start".
Link to reference for creating WAS service commands: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rins_wasservice.html.
Note: wasservice commands are case sensitive, so you will need to run each as specified in the Infocenter. For Example:
WASService -add
-profilePath profile_root
-wasHome app_server_root
Resolving the problem
Further troubleshooting WAS:
1. Recreate issue with WASService commands.
2. Verify client creating service commands properly (see example above).
3. Issue either the start or stop command.
Review the log files for the point of failure.
This happens when no default record type is defined in your schema. This issue has been identified as a product defect under APAR PK78422.
This problem occurs in ClearQuest Web version 7.1.x.
Diagnosing the problem
Determine whether a default record type has been selected. In ClearQuest Designer, you can right-click on each record type to see if it has been designated a default record type.
Resolving the problem
This defect is under investigation. There is no permanent fix at this time.
To workaround this problem, designate one of your record types as a default record type.
What steps can you follow to gather additional information for IBM Rational ClearQuest Support in resolving issues with the ClearQuest Web 7.1.x?
Default Installation Locations
These are the default installation directories for Rational home and Rational common components. If you are using a non-default installation path, keep that in mind when reviewing these instructions.
RATIONAL_HOME refers to the location where Rational products are installed.
RATIONAL_COMMON refers to the location where common components are installed.
Note: On some UNIX operating systems, the path might have a lowercase "ibm" directory. You can also access the Rational home and common directories using these symbolic paths:
Basic Verification Information
Note: With steps 2 through 5, if you do not receive the expected verification that the software is running correctly, take a screenshot or save the message to file for IBM Support.
1. Check that the system requirements are met. For more information, see technote 1294762.
2. Verify that IBM HTTP Server is running by accessing this URL:
If the service is running correctly, you
will see this welcome message:
Rational Web Platform: If
you see this page, it means that Rational Web Platform was installed and is
running on this system.
3. Verify that CM Server is running by accessing this URL:
If the service is running correctly, you
will see this welcome message:
Hi there, this is a Web
4. Verify
that the ClearQuest Web application is running by accessing this URL:
If running, you will see the ClearQuest Web interface and login screen appear.
5. Verify that the RPC services are running. Refer to the Checking RPC servers topic in the ClearQuest Information Center for details.
Gathering Diagnostic Logs for ClearQuest Web on Microsoft Windows
1. Login to ClearQuest Web as a Super User. Access the Site Administration > Site Configuration screen. Under the Application Options tab, set the Enable Diagnostics value to full.
2. If requested by a ClearQuest Support Engineer, refer to the CM Server Diagnostic Logging and Information section for instructions on increasing the CM Server logging levels.
3. Stop the CM Server and ClearQuest Web services. Refer to the Starting, stopping, and restarting CM Server topic of the ClearQuest Information Center.
Note: This will also stop the ClearCase Remote Client (CCRC) server and CM API operations if hosted on the same machine.
If installed, also disable the service for full-text searching.
4. Delete any existing logs from these directories:
5. Enable
diagnostic tracing. Download the file core_trace_for_web.zip from
this technote. Extract the core_trace_for_web_enable.reg file
onto your Web server. Double-click on the file to update the Windows registry.
6. Restart all the web services except for full-text search.
7. Reproduce the problem behavior with ClearQuest Web.
8. Stop all web services again.
9. Gather all the logs in these directories:
· <RATIONAL_COMMON>\IHS\logs
If instructed by a ClearQuest Support
Engineer, gather the CM Server MBean configuration data. You can find
instructions in the CM Server Diagnostic
Logging and Information
Also collect the trace file, which should be located in the root C: drive directory.
10. Disable diagnostic tracing. Extract the core_trace_for_web_disable.reg file onto your Web server. Double-click on the file to update the Windows registry.
11. Restart all necessary web services.
12. If you adjusted the logging levels for CM Server, you must restore the original settings. See the CM Server Diagnostic Logging and Information section for instructions.
13. Login to ClearQuest Web as a Super User. Access the Site Administration > Site Configuration screen. Under the Application Options tab, set the Enable Diagnostics value to default.
14. You may now resume normal ClearQuest Web operation.
Gathering Diagnostic Logs for ClearQuest Web on Linux or UNIX
1. Login to ClearQuest Web as a Super User. Access the Site Administration > Site Configuration screen. Under the Application Options tab, set the Enable Diagnostics value to full.
2. If instructed by a ClearQuest Support Engineer, refer to the CM Server Diagnostic Logging and Information section for instructions on increasing the CM Server logging levels.
3. Stop the CM Server and ClearQuest Web services. Refer to the Starting, stopping, and restarting CM Server topic of the ClearQuest Information Center.
Note: This will also stop the ClearCase Remote Client (CCRC) server and CM API operations if hosted on the same machine.
4. Delete any existing logs from these directories:
· <RATIONAL_COMMON>/IHS/logs
5. Enable diagnostic tracing.
Modify the file cqrpc.sh, which is found in this directory:
If they do not exist, add these six lines to the end of the file:
export CQ_DIAG_TRACE
export CQ_DIAG_REPORT
export CQ_DIAG_OUTPUT
If these lines already exist in the file, then they are likely commented out. If so, uncomment the lines.
Note: If the install directory is different than indicated, modify the CQ_DIAG_OUTPUT to account for the correct cmprofile logs directory.
6. Restart all the web services except for full-text search.
7. Reproduce the problem behavior with ClearQuest Web.
8. Stop all web services again.
9. Gather all the logs in these directories:
· <RATIONAL_COMMON>/IHS/logs
If instructed by a ClearQuest Support Engineer, gather the CM Server MBean configuration data. You can find instructions in the CM Server Diagnostic Logging and Information section.
If you defined a directory other than the cmprofile logs directory for the diagnostic trace output, collect the logs from that directory.
10. Disable diagnostic tracing by commenting out all six diagnostic lines in the cqrpc.sh file.
11. Restart all necessary web services.
12. If you adjusted the logging levels for CM Server, you must restore the original settings. See the CM Server Diagnostic Logging and Information section for instructions.
13. Login to ClearQuest Web as a Super User. Access the Site Administration > Site Configuration screen. Under the Application Options tab, set the Enable Diagnostics value to default.
14. You may now resume normal ClearQuest Web operation.
Change Management (CM) Server Diagnostic Logging and Information
In some instances, it is necessary to gather diagnostic information on CM Server as well as ClearQuest Web. These sections instruct you on how to prepare this diagnostic information for gathering along with the ClearQuest Web information. You should only follow these instructions at the request and guidance of a ClearQuest Support Engineer.
Collecting MBean attribute information
You can configure CM Server using a variety of different variables called MBean attributes. When experiencing problems with ClearQuest Web or CM Server, it is worth verifying that these attributes are correctly established. Incorrect attribute values can cause problems with the starting or stability of the server processes.
You can send IBM Rational Support a summary of your custom MBean configuration settings with these instructions:
1. Locate
these directories:
Windows: <RATIONAL_COMMON>\CM\profiles\cmprofile\config\cells\<host>CMProfileNode01Cell\nodes\<host>CMProfileNode01Cell\servers\server1\stp
Linux/UNIX: <RATIONAL_COMMON>/CM/profiles/cmprofile/config/cells/<host>CMProfileNode01Cell/nodes/<host>CMProfileNode01Cell/servers/server1/stp
Note: If the "stp" directory does not exist, you have not established any custom MBean attributes. You do not have to continue with gathering this particular data.
2. These files store the current MBean attributes configured for CM Server. Collect all of the files in this directory.
More information on proper MBean configuration
You can find more information about this in these documents:
· The Setting available MBean attributes topic in the ClearQuest Information Center.
· Technote 1384746 - Preserve the CM Server MBean Configuration Before Customizing the MBean Attributes, Upgrading, or Reinstalling ClearCase and ClearQuest.
Increasing CM Server logging levels
These are the steps for increasing the logging level detail on CM Server. By changing the logging level, you are increasing the trace output and diagnostic information in the CM Server logs. With these instructions, you will also verify that file count and file size of these logs is sufficient for reproducing a problem during a trace.
Increasing the diagnostic detail can affect system performance. This should only be done for short periods of time. Be sure to restore logging to original settings when such detail is not needed.
1. Browse to the CM Server administration console URL:
Note: The default port is 12060 for out-of-the-box CM Server. For CM Server hosted on your own IBM WebSphere Application Server, the default port is 9060.
2. Login to the administration console.
3. Access the menu option Troubleshooting > Logs and Trace.
4. Click on your server. The default for out-of-the-box CM Server is server1.
5. Click on Diagnostic Trace.
6. Under the Runtime tab, change the Maximum File Size and Maximum Number of Historical Log Files values to 20. Click OK at the end of the page.
7. Click the Save link in the Messages area at the top of the page that opens.
8. Click on JVM Logs.
9. Under the Configuration tab, change the Maximum Size and Maximum Number of Historical Log Files values to 20. Do this for both error log files, System.out and System.err. Click OK at the end of the page.
10. Click the Save link in the Messages area at the top of the page that opens.
11. You will need to restart the CM Server process for these changes to take affect.
12. Once restarted, return to the CM Server administration console.
13. Access the menu option Troubleshooting > Logs and Trace.
14. Click on your server. The default for out-of-the-box CM Server is server1.
15. Click on Change Log Detail Levels.
16. Under the Runtime tab, expand the com.ibm.rational.* group.
17. Click on the com.ibm.rational.stp.* sub-group. Select the context menu item Message and Trace Levels > fine. Click OK at the end of the page.
18. Click the Save link in the Messages area at the top of the page that opens.
Restoring standard CM Server logging levels
These are the steps for restoring the logging levels of CM Server to their original state.
1. Browse
to this URL:
Note: The default port is 12060 for out-of-the-box CM Server. For CM Server hosted on your own IBM WebSphere Application Server, the default port is 9060.
2. Login to the administration console.
3. Access the menu option Troubleshooting > Logs and Trace.
4. Click on your server. The default for out-of-the-box CM Server is server1.
5. Click on Change Log Detail Levels.
6. Under the Runtime tab, expand the com.ibm.rational.* group.
7. Click on the com.ibm.rational.stp.* sub-group. Select the context menu item Message and Trace Levels > info. Click OK at the end of the page.
8. Click the Save link in the Messages area at the top of the page that opens.
Related information
MustGather: ClearQuest Web Java
acies in, or any omissions from, the information which it contains.
What are the details on configuring the IBM® Rational® ClearQuest® 7.1.x server to use an alternate HTTP port other than port 80?
The Changing the default CM Server HTTP port and Changing the default CM Server ports topics in the ClearQuest Information Center have detailed information on changing port numbers for ClearQuest Web and CM Server. This a summary of the required steps
To change the ClearQuest 7.0.x Web services to use an alternate HTTP port, there are 3 files that need updating. This is an example of changing the port to from the default of 80 to 8080.
httpd.conf - Location: (C:\Program Files\IBM\RationalSDLC\common\IHS\conf) - You must change
the following line at the Listen directive:
2. plugin-cfg.xml - Location (C:\Program Files\IBM\RationalSDLC\common\eWAS\profiles) - Update port where the VirtualHost name is set to 80.
3. virtualhosts.xml - Location (C:\Program Files\IBM\RationalSDLC\common\CM\profiles\cmprofile\config\cells\<node_name>) - Update HostAlias_2 where the entry is 80.
Stop all ClearQuest Web services before updating the files and then restart them after you have updated the files. When you now try to access ClearQuest Web, you must use the URL including the port number:
If the ClearQuest Web fails to start, try re-booting the server to fully release the ports.
System Resources
All Platforms
CM Server host must have a minimum of 4 GB of memory.
Java Virtual Machine (JVM) cache for the CM Server profile must be 1 GB.
At a minimum, the swap space on UNIX host systems must be twice the size of memory.
Disable the Nagel algorithm by using the following command:
ndd -set /dev/tcp tcp_naglim_def 1
Use an AIX Power 5 or Power 6 host system.
Set the following operating system parameters:
no -o tcp_nagle_limit=0
Most TCP
implementations use the Nagel algorithm, where a TCP connection can have only
one outstanding small segment that has not been acknowledged. This causes TCP
to delay sending further packets until it receives an acknowledgement or until
it can bundle more data and send a full-size segment.
You must disable the Nagel algorithm when using the ClearQuest Web application.
no -o clean_partial_conns=1
Specifies whether
SYN (synchronize the sequence number) attacks are avoided.
Enable this option for the ClearQuest Web application to protect against network attacks.
no -o tcp_nodelayack=1
Enabling this
parameter causes TCP to send immediate acknowledgement (ACK) packets to the
sender. When the parameter tcp_nodelayack is off, TCP delays sending ACK
packets by up to 200 ms. This allows the ACK packet to piggyback on a response
and minimizes the system overhead.
For optimal performance, enable this parameter.
no -o rfc1323=1
Enables window
scaling and time stamps as specified by RFC 1323 (TCP Extensions for High
Performance). Window scaling allows the TCP window sizes (tcp_recvspace and
tcp_sendspace) to be larger than 64 KB (65,536) and is typically used for large
maximum transmission unit (MTU) networks.
If your ClearCase VOBs or ClearQuest databases are hosted on a Windows system, enable this parameter for optimal performance.
Increase the following tunable kernel parameters:
Disable the Nagel algorithm by issuing the following command:
ndd -set /dev/tcp tcp_naglim_def 1
Modify TCP_KEEPALIVE_INTERVAL (Determines the interval between probes)
ndd -set /dev/tcp tcp_keepalive_interval 7200000
default value: none
value: 7200000 (milliseconds)
Increase JVM VIRTUAL PAGE SIZE(Sets the JVM instruction and data page sizes to 64 MB to improve performance)
For WebSphere 6.1.0.x use the following command
chatr +pi64M +pd64M <WASHOME>/java/bin/PA_RISC2.0/java
default value: 4 MB
recommended value: 64 MB
Stop WAS prior to making this change.
Modify TCP_CONN_REQUEST_MAX
Specifies the maximum number of connection requests that the operating system can queue when the server does not have available threads. When high connection rates occur, a large backlog of TCP/IP connection requests builds up and client connections are dropped. Adjust this setting when clients start to time out after waiting to connect. Verify this situation by issuing the netstat -p tcp command. Look for "connect requests dropped due to full queue."
ndd -set /dev/tcp tcp_conn_request_max 8192
default value: 4096
recommended value: 8192
CM Server Parameters
The CM Server may be tuned for optimal performance for ClearQuest Web users based on expected peak load. The following parameter list can be adjusted to achieve the desired performance level. See the CM Server documentation in the ClearQuest Web administrator help for instructions on how to modify these MBEANs.
serverWorkerThreadCount - Default value is 16
Description : The number of threads that a ClearQuest RPC process will use to handle incoming requests.
Configuration : Increasing this value allows for a fewer number of ClearQuest RPC processes. Update this value with caution, as setting it to an improper value can have a negative effect on performance. Setting this value too high will cause contention within a process, and setting this value too low increases the need for more ClearQuest RPC processes.
activeHttpSessionThreshold - Default value is 30.
Description : The number of active HTTP sessions on a ClearQuest RPC process. If this value is exceeded, it may cause the CM Server to start another ClearQuest RPC process.
Configuration: Increasing this value will allow for fewer ClearQuest RPC processes. Update this value with caution, as setting it too high will cause contention within a process, and setting it too low will increase the need for more ClearQuest RPC processes.
maximumActiveServers - Default value is 8.
Description : The maximum number of active ClearQuest RPC processes allowed by the CM Server. This number may be adjusted to suit the host system's resource capacity.
recycleServerHttpSessionLimit - Default value is 200. A value of zero indicates that this limit will not be checked.
Description : The number of HTTP sessions that a ClearQuest RPC process will service before it is recycled by the CM Server.
recycleServerLifetimeLimit - Default value is 86,400 seconds (24 hours). A value of zero indicates that this limit will not be checked.
Description : The maximum life time, in seconds, of a ClearQuest RPC process before it is recycled by the CM Server.
recyclingPeriod - Default value is 3,600 seconds (60 minutes). This value must be greater than zero.
Description : The amount of time, in seconds, that a recycling ClearQuest RPC process is allowed to shutdown and complete any outstanding session work before it terminates.
Configuration: Update this value with caution, as setting this to an improper value can have a serious effect on performance. This value overrides the behaviors of the following MBEANs: sessionObjectDefaultTimeout, sessionQueryObjectTimeout, and sessionRecordObjectTimeout.
The IBM Rational ClearQuest Web Server is dependent on the CM Server. When you install IBM Rational ClearQuest Web Server, you must either install CM Server on the same system or have a CM Server available on a different system.
Resolving the problem
To workaround this issue, install CM Server on the same server as the ClearQuest Web Server. Or install CM Server on a different server that is accessible by the ClearQuest Web Server.
What are the details on configuring the IBM® Rational® ClearQuest® 7.0.x Web Java server to use an alternate HTTP port other than port 80?
The To change the default RWP HTTP port and To change the default RWP ports topics in the ClearQuest Information Center have detailed information on changing port numbers for ClearQuest Web and the Rational Web Platform (RWP). This a summary of the required steps.
To change the ClearQuest 7.0.x Web services to use an alternate HTTP port, there are 3 files that need updating. This is an example of changing the port to from the default of 80 to 8080.
httpd.conf -
Location: ( c:\program files\rational\common
\rwp\IHS\conf) - You must change the following line at the Listen directive:
2. plugin-cfg.xml - Location (c:\program files\rational\common\rwp\EmbeddedExpress\profiles) - Update port where the VirtualHost name is set to 80.
virtualhosts.xml -
Location (c:\program
\profile1\config\cells\DefaultNode) - Update HostAlias_2 where the entry is 80.
Stop all ClearQuest Web services before
updating the files and then restart them after you have updated the files. When
you now try to access ClearQuest Web, you must use the URL including the port
If the ClearQuest Web fails to start, try re-booting the server to fully release the ports.
Level: Introductory
Carlos Ferreira, Product Manager, IBM
06 Aug 2004
In this whitepaper Carlos Ferreira provides information on how to configure your environment to optimize performance of the new IBM Rational ClearQuest Web.
The intent of this whitepaper is to provide IBM® Rational® ClearQuest® Web administrators with system monitoring, tuning, and sizing information. This document applies to ClearQuest Web version 2003.06.00.500 (not to previous versions of ClearQuest Web, which were based on Active Server Pages technology). In order to optimize the performance of ClearQuest Web effectively, it is important to understand the concepts described here. From a top level point of view, the primary areas to consider in a ClearQuest Web deployment are:
In addition, these important considerations are covered in a separate Rational ClearQuest performance white paper entitled "Rational ClearQuest Performance Improvement" by James Tykal, Senior Technical Marketing Engineer:
In order to tune and size a ClearQuest Web application deployment effectively, you must first ensure that you have monitoring tools in place. They will measure critical performance parameters for each of the above areas, and are also useful for troubleshooting production performance problems.
Monitoring tools are dependent on the operating system on which you are deploying ClearQuest Web. The specific tool(s) you should use are naturally dependent on which ClearQuest Web component you are monitoring. In any case, your monitoring process should include storing results for specific configurations so that you can see performance trends over time.
Memory and CPU Usage
Operating system resources like process memory and CPU use are among the most important parameters to measure. Average CPU utilization of greater than 90% may be unhealthy-an indication that peak CPU usage of 100% is occurring. This may cause sporadically slow transaction response times and inconsistent memory usage patterns. To help you track this, Microsoft® Windows® comes with a performance monitoring tool that is available in the Microsoft Management Console. To launch the performance tool, type the following either in the Run dialog box or the at the MS-DOS prompt:
For additional details on how to use this performance monitoring tool see the MSDN library performance tools page.
To measure UNIX® operating system resources, the top command is a useful performance monitoring tool. For additional details on how to use the top command, see: http://www.mcsr.olemiss.edu/cgi-bin/man-cgi?top+1 Table 1, following, shows some typical output of the top command.
Figure 1. Example output from UNIX top command table 1
Tables 2 and 3 show key ClearQuest Web processes to monitor.
Table 2. ClearQuest Web application processes on Windows
Additional information
Rational Web Platform, Apache HTTP server
There are two
rwp.exe processes for fault tolerance; one is master, one is worker. If the
worker process dies, the master starts up a new one.
Rational Web Platform, Tomcat servlet engine for ClearQuest Web
The properties
file that controls these Java processes is
Rational Web Platform, Tomcat servlet engine for ReqWeb
ClearQuest Web does not use this service.
Table 3. ClearQuest Server process on Windows
Additional information
The properties
file that controls these Java® processes is
Renaming ClearQuest Java Processes on Windows for Easier Monitoring
In Tables 2 and 3 above, there are four different ClearQuest Web processes called java.exe, which makes it difficult to isolate and monitor specific ClearQuest processes. To clarify their function, you should rename the processes specified in the bootstrap files shown on Table 4. The three steps required to rename a ClearQuest Java process are:
1. Rename the Java executable in the bootstrap file that initiates the process.
2. Create a copy of the java.exe program with the new name.
3. Restart the services.
Table 4. Java process bootstrap properties files
CQWJ Java Process
Bootstrap Filename and Location
Registry Server
Request Manager
1. Modify the following section in each bootstrap file:
# This is the Java interpreter used for running Tomcat
2. Change the
java.exe file name to something more meaningful, such as
java_requestmgr.exe for the Request Manager. If you are working with a multiple
Request Manager configuration, name each Request Manager process uniquely, such
3. Create copies of the actual
java.exe program and give the copies the same names as the renamed
processes. The
java.exe program used by ClearQuest Web Application is in
C:\Program Files\Rational\Common\Java\JRE\bin. Simply duplicate this program and rename the copy. Be
sure to keep the original
java.exe in this directory.
4. Restart all the ClearQuest Web processes to have the renamed
processes take effect. You can use Windows Task Manager to examine the renamed
processes. On UNIX, the command
ps -ef | grep java will provide all the java processes that are running, along
with their executable directory and process ID. The process ID can then be
correlated with the process ID provided in the top command. Table 5 shows the
Java process directory and the component to which it corresponds.
On UNIX, conversely, renaming the Java processes is not necessary because the process IDs can be determined from the information detailed in Table 5.
Table 5. ClearQuest Web application processes on UNIX
Additional information
Rational Web Platform, Apache HTTP server
On UNIX, the
rwp processes are collectively one instance of Apache. Apache consists of one
master process and several worker processes (instead of one master and one
multi-threaded worker like that running on Windows). You can tune the number
of worker rwp processes by editing the
Rational Web Platform, Tomcat servlet engine
The word "arch" represents the architecture for example, sun5 for Sun Solaris.
Registry Server
Process ID can
be found in the file
Request Manager
Process ID can
be found in the file
When you are seeking to understand system performance, the number of concurrent users accessing the ClearQuest Web application during a performance test is an important metric to capture. Table 6 below provides access log information for Apache and Tomcat.
Apache access log containing the list of IP addresses that have accessed ClearQuest Web and when they accessed it.
Tomcat access log
access.log file contains the client IP addresses, as well as the times
that the clients have accessed the application. Here is an example of the
192.168.223.1 - - [23/Aug/2003:17:36:37 -0400] "GET
bd99-c0a8df01e187 HTTP/1.1" 200 1571
192.168.223.1 - - [23/Aug/2003:17:36:37 -0400] "GET
FAll%20Defects HTTP/1.1" 200 519
192.168.223.1 - - [23/Aug/2003:17:36:38 -0400] "GET
e8746e42-eb91-4773-bd99-c0a8df01e187 HTTP/1.1" 200 1151
192.168.223.1 - - [23/Aug/2003:17:36:38 -0400] "GET /common/html/null.html
Other important values to monitor include:
You can monitor
active HTTP sessions-using the RWP Tomcat servlet access logging -- by
C:\Program Files\Rational\Common\rwp\conf\server.xml. For more information go to: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/valve.html#Access%20Log%20Valve
You can log the following items:
You can also monitor the current status of your HTTP Web server using the following URL: http://Hostname/server-status, where Hostname is the name of the server on which ClearQuest Web is deployed. The following information is provided:
The following
additional information can be accessed by adding the ExtendedStatus On
directive to the
C:\Program Files\Rational\Common\rwp\conf\rwp.conf, as shown below.
# Directives related to inquiring server status
ExtendedStatus On
Other key indicators to consider when monitoring web applications include transaction response times and transaction throughput. There are many software tools available that allow you to simulate user transaction load on your ClearQuest Web deployment. Note that these tools often require that you record or build scripts that reflect your user transaction load profile. They also provide metrics regarding the number of transactions that succeed or fail, and the average, minimum, and maximum response times per transaction. Monitoring these transactions is an important step in being able to size your hardware for your production deployment effectively. In fact, IBM® Rational® Test Manager ™ was used to test the performance of the IBM Rational deployment of ClearQuest Web.
Rational ClearQuest Web Application
The ClearQuest Web application and the ClearQuest Server are the two installable components of the latest version of ClearQuest Web. The ClearQuest Web application installs the RWP (including Apache version 2 and Tomcat version 4), which is the common web platform for serving the IBM® Rational® RequisteWeb®, ClearQuest Web, IBM® Rational® ClearCase® Web, and IBM® Rational® Project Console™ web clients. The ClearQuest Web Application is the presentation tier of the ClearQuest Web, deployed as a web application on the Tomcat servlet engine. Some ClearQuest Web static HTML and Javascript files are also deployed on the Apache Web Server.
When tuning the ClearQuest Web deployment, do not change too many configuration parameters at one time. After making a change, monitor the application using monitoring tools described in the previous section.
As opposed to the software configuration, the single biggest hardware issue affecting ClearQuest Web performance is RAM. If multiple applications are using a server that lacks available memory or CPU resources, the most likely result is poor performance. To ensure that there is adequate memory and CPU available for each ClearQuest process deployed on the server, use the monitoring tools described in the previous section to determine which processes are consuming memory and CPU. With this information, you can stop or move unnecessary processes to a different server to conserve memory or CPU. In addition, you can increase the maximum JVM memory for each of these processes to eliminate Out of Java Memory Error or OutOfMemoryException reported in the log files.
For the peak number of concurrent clients, you should ensure there is a sufficient memory for Apache, Tomcat, Request Manager, and Registry Server processes by looking at your process list using a tool such as top. If you deploy all of these applications on the same server, their total memory should not be more than 80% of the total available memory, since some memory needs to remain available for the operating system processes. Finally, run the latest stable release and patch level of the operating system that you choose. Many OS suppliers have introduced significant performance improvements to their TCP stacks and thread libraries in recent years.
Reduce the Amount of Logging
Logging to files
requires the use of system resources: disk, memory, and CPU. Excessive logging
degrades performance, and the sheer number of log entries can also make it more
difficult to find problems. Logging should be set to
<logger level="SEVERE"/> when trying to troubleshoot problems in production. See the
ClearQuest Web Administrator's Guide (in Additional References, following) for
instructions on how to set the logging level for all ClearQuest Web Application
components. As log files increase in size, however, performance will degrade.
You should therefore rotate log files every 24 hours. With the RWP, ClearQuest
Web provides utilities to do so.
Tuning Apache
This section covers some of the more important tuning parameters of the Apache HTTP server. For a complete list of all the parameters that can affect performance, see the Apache Web site. You can obtain significant performance gains simply by ensuring that settings are correctly configured for the expected application load. Since every ClearQuest Web client's request goes to the Apache HTTP server first, its performance plays an important role in the overall system operation.
Secure Sockets Layer (SSL)
If SSL client authentication is configured, the server requests the client's certificate for any HTTPS (HTTP + SSL) request. This of course adds overhead and therefore decreases system performance. If you don't need SSL, you can disable SSL connections in the Apache Web server. See the New ClearQuest Administrator's Guide for information about enabling and disabling SSL Connections in Apache.
KeepAlive Directive 2
This directive
enables HTTP persistent connections. The syntax is:
KeepAlive On|Off Default: KeepAlive On
The Keep-Alive
extension to HTTP/1.0 and the persistent connection feature of HTTP/1.1 provide
long-lived HTTP sessions, which allows multiple requests to be sent over the
same TCP connection. In some cases this has been shown to result in an almost
50% speedup in latency times for HTML documents with many images. To enable Keep-Alive
connections, set
KeepAlive On.
A Web server should never have to swap, as swapping increases the latency of each request beyond a point that users consider "fast enough". This causes users to hit stop and reload, further increasing the load. You can, and should, control the MaxClients setting to prevent your server from spawning so many children that it starts swapping. This directive specifies the maximum number of child processes that will be created to serve requests, and limits the number of simultaneous requests that will be served. Any connection attempts that are over the MaxClients limit will normally be queued, up to a number based on the ListenBacklog directive. You should set this to the maximum number of clients that your environment can manage without experiencing throughput degradation or a prohibitive increase of the response time.
ExpiresByType Directive
A major
performance gain in high latency environments is possible if you add the Mod_Expires
Module to the RWP, and modify the web application configuration to utilize the ExpiresByType
directive. These directives will reduce the number of round trips from the
client browser to the RWP Apache Web server. A web server has the option to
tell the browser how long it should cache content. By default, the RWP Apache
does not tell the browser anything about when the content should expire, which
basically means that the browser determines (through its own heuristic
algorithms) when the content will expire. When the browser checks for a new
version, it sends a condition
get request ("send me a new copy of this file if your copy
is newer than mine"). However, since the server is rarely updated it
almost always responds with a 304 response, which tells the browser it already
has the latest version. All of these 304 requests are essentially wasted
requests since there is no new data returned. The ExpiresByType
directive may be added to the ClearQuest Web in a future release.
Tuning Tomcat
Setting the Servlet Queue Size
The maximum
number of concurrent connections that a servlet is allowed to handle should
typically be lower than the total number of http threads. This is because not
all the requests take the same time to fulfill. Some requests may require a
limited amount of computing power, while other HTTP requests may simply need an
HTML page. ClearQuest Web includes the Apache and Tomcat versions that support
the AJP 1.3 and 1.4 protocols, and the <connector> element of Tomcat's
server.xml file tells Tomcat to listen for AJP requests. The
maxProcessors attribute of the <connector> element represents the
maximum number of request processing threads that this connector can create,
which therefore determines the maximum number of simultaneous requests that can
be handled. The default value is 75. To change this value, edit the
\Rational\Common\rwp\conf\server.xml file
You can
configure the available minimum and maximum Java Virtual Machine (JVM) memory
used by Tomcat on Windows by modifying the
Files\Rational\Common\rwp\bin\jk_service.properties file. Modify the section shown below:
# JVM Options
# Useful Options:
# -Xms2m = Initial heap size, modify for desired size
# -Xmx256m = Maximum heap size, modify for desired size
For UNIX, modify
setclasspath.sh script, which is in
As an example of how much memory you may require, performance tests completed using an example customer schema showed that approximately 400 kilobytes of memory per user was required for the CQ Web application session on the Tomcat servlet engine. The steady state memory usage without any users was approximately 60 megabytes.
Garbage Collection
The best way to optimize garbage collection is through testing. You'll want to set the minimum and maximum JVM memory size close to one another, because JVM maximum and minimum memory settings that are too far apart will cause the garbage collector to run less frequently, and will therefore require more time and CPU resources to collect more objects. Garbage collections with a frequency of less than one minute should produce a good result. To determine the duration between garbage collection intervals, measure the time between major decreases in Java process memory.
The ClearQuest Server includes two components: the Request Manager and the Registry Server. The Registry Server is a software load-balancer process that directs requests from the ClearQuest Web application (deployed on the Tomcat servlet engine) to the Request Manager(s). The Request Manager stores a user's ClearQuest session. The Request Manager is responsible for activities like submitting, modifying, viewing, and deleting queries and records in the ClearQuest database.
A thread is a
unit of processing capacity available to perform computing within the JVM. The
greater the number of threads the higher the CPU load. In cases where CPU load
is high, and the ClearQuest Web application is CPU-bound, the number of threads
should be reduced. In cases where CPU usage is low, on the other hand, you can
increase the number of threads to handle more user or transaction load. When
increasing the number of threads, check to make sure that there is adequate
memory available for the Request Manager to handle the additional concurrent
load. In order to understand how to modify the ClearQuest Web thread parameters
described below, see the Rational ClearQuest Web Administrator's Guide (the Customizing
jtl.properties File section, as well as Table 5,
jtl.properties File Locations).
MAXSERVICEREQUESTTHREADS -- This specifies the maximum number of concurrent
ClearQuest Web application requests that the Request Manager can process.
Although you can increase this value to try to minimize the queued time for
multiple requests, the default value for this property is set to five based on
the assumption that ClearQuest Web is deployed on a machine with one CPU. This
is because testing suggests that this is the optimal number of threads for one
CPU. On a single-CPU machine, setting this value to less than five might result
in under-utilization of system resources, while increasing it to more than five
might result in slight degradation in the response times.
If the ClearQuest Server is deployed on a single-CPU machine, use the default value. If the machine has more than one processor, then modify this setting to five times the number of CPUs, i.e., 5 * #CPUs. For example, if the ClearQuest Server is installed on a four-processor machine, modify this setting to 20.
MAXSERVICERESPONSETHREADS -- this is the number of threads sending responses back to
the various requestors. The default value is two, again for a single-CPU
machine. This value should be changed to reflect two times the number of CPUs.
For example, on a four-CPU machine, this value should be set to eight.
Testing with an
example customer schema on a four-CPU server with
MAXSERVICEREQUESTTHREADS set to thirty, fourteen simultaneous users successfully
preformed a submit action all within thirty seconds. In cases where
MAXSERVICEREQUESTTHREADS is not set high enough, you may see errors like Failed
to execute use case 'cq_getworkspace_folder'. String index out of range: -1.
RPCREQUESTTIMEOUTSECOND -- This setting defines the amount of time in seconds that
the ClearQuest Web application waits for the Request Manager to processes
requests. If the ClearQuest Web application does not receive the response from
Request Manager in the time defined by this setting, it times out and notifies
the user. The default value for this timeout is set to 90 seconds. Ideally, a
request should not require 90 seconds to process. The Request Manager processes
most of the requests it receives in just a few seconds. However, there might be
some scenarios where the requests take a very long time. For example, a query
that is searching for a word in the description area of all the defects might
take longer then 90 seconds, and would result in a timeout. Similarly,
submitting a defect that has a lot of hooks in it could result in a long
processing time on the Request Manager, again resulting in a timeout.
Increasing this setting might provide an easy temporary resolution for the time-out error, but it would be the wrong solution for end users. For example, setting this value to 300 seconds would result in users having to wait five or more minutes for a query or record operation. The right solution is to find which queries, records, or hooks are taking a long time to execute, determine why, and resolve the problem. Ask yourself whether the filter criteria are badly defined and overly complex, or if there are there too many hooks into the record. Settling these types of issues could provide a permanent solution that is more responsive, requires less system resources, and has fewer time-out errors.
It is likely
that you will have to modify the Request Manager memory to reflect your
deployment characteristics. You can configure the available minimum and maximum
JVM memory used by the ClearQuest Request Manager by modifying the file named
C:\Program Files\Rational\ClearQuest\cqweb\cqserver\
requestmgr_service.properties. For UNIX, modify
/opt/rational/clearquest/cqweb/cqserver/start_cqrm.sh Modify the section shown below:
# JVM Options
# Useful Options:
# -Xms2m = Initial heap size, modify for desired size
# -Xmx256m = Maximum heap size, modify for desired size
Again as a guideline, testing showed that the ClearQuest Request Manager steady-state memory usage with one user was approximately 60 megabytes. Performance tests done using an example customer schema showed that ClearQuest Request Manager required 5 to 12 megabytes of additional memory for each additional user doing 15 transactions per hour.
It is not likely
that you will have to modify the Registry Server memory. Nevertheless, the
available minimum and maximum JVM memory used by the ClearQuest Registry Server
can be set by modifying
C:\Program Files\Rational\ClearQuest\cqweb\cqregsvr\
cqregsvr_service.properties. For UNIX, modify
/opt/rational/clearquest/cqweb/cqregsvr/start_cqreg.sh. Modify the section shown below:
# JVM Options
# Useful Options:
# -Xms2m = Initial heap size, modify for desired size
# -Xmx256m = Maximum heap size, modify for desired size
The ClearQuest Registry Server steady state memory usage with one user was approximately 20 megabytes. Performance tests done using an example customer schema showed that for each additional user, ClearQuest Registry Server needed a negligible amount of additional memory.
Tuning the Network Configuration
While this paper's intent is not to provide a comprehensive guide for tuning your network, this section will provide information on some quick ways to diagnose network configuration issues that may cause performance problems with the new ClearQuest Web.
Network Latency
Poor network performance may cause performance degradation of any web application. When troubleshooting performance problems with the new ClearQuest Web, you should verify network latency between:
Since the new ClearQuest Web Application installs the Web Server (Apache) and servlet engine Server (Tomcat) on the same server, you don't have to verify item 2. However, this may be applicable in cases where a customer has installed a proxy web server between the web client making the HTTP request and the ClearQuest Web Application Server. These proxy web servers are sometimes used with firewalls for security purposes, or to provide a software load-balancer with multiple ClearQuest Web Clusters.
Determining Network Latency
Network latency can be determined by typing the ping command at the starting server and then the name of the target server between which you are trying to determine the latency. You must determine the latency between each server. The results below are from a ping command.
ping sus-ma1ratlt2
Pinging sus-ma1ratlt2 [220.127.116.11] with 32 bytes of data:
Reply from 18.104.22.168: bytes=32 time=125ms TTL=119
Reply from 188.8.131.52: bytes=32 time=127ms TTL=119
Reply from 126.96.36.199: bytes=32 time=125ms TTL=119
Reply from 184.108.40.206: bytes=32 time=126ms TTL=119
Ping statistics for 184.108.40.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 127ms, Average = 125ms
If the combined network latency between the web client, ClearQuest Web Application, Request Manager, and the Database Server is greater than 200 milliseconds, ClearQuest Web transaction performance can degrade. Note that performance problems associated with ClearQuest Web login are often caused by latency between the Request Manager Server and the Rational Common License Server. In addition, ping statistics revealing packets being lost at a rate greater than 5 percent could also indicate degraded ClearQuest Web transaction performance. Consult your network administrator to resolve network latency and lost packets concerns.
Tuning the Rational Common License Server
ClearQuest Web uses the Rational Common License Server based on FlexLM from Globetrotter Software. Rational provides tools to monitor and administer your ClearQuest licenses. One tool is LMTools by Globetrotter Software, which provides License Server status and server diagnostics. To improve the performance of your ClearQuest deployment, ensure that there is good network connectivity between the Request Manager and ClearQuest License Server. As mentioned above, network connectivity should have a latency of less than 200 ms and very few or no dropped packets. Furthermore, performance testing has revealed that each additional license server causes the login transaction response time to reduce an additional four seconds. Also consider co-locating your license server with your Request Manager.
Additional time to check out a license is required at sites that have deployed the new ClearQuest Web with ClearQuest MultiSite. A MultiSite license is checked out when the user logs in. A ClearQuest license, on the other hand, is checked out when the user selects the user database.
Licenses are checked out only once. The ClearQuest Web Application does not have to have network connectivity to the license server, only the Request Manager does.
Hardware Sizing for a ClearQuest Web Deployment
Server sizing to meet performance needs is unique to each customer's deployment environment. Performance is highly dependent on a customer's database schema, usage, web server configuration, database configuration, and network configuration. The IBM Software Group does not give customer-specific recommendations for sizing or quantifying how much or what type of hardware a customer needs to meet specific ClearQuest Web transaction load or performance criteria. In order for customers to determine their hardware requirements to deploy ClearQuest Web, they should start with the minimum recommended hardware outlined in the installation guide. Then, they should execute performance tests to determine how many concurrent users can be accommodated while maintaining their desired transaction response times and transaction rates for a single-server environment.
Quantifying the number of concurrent users per server allows you to calculate how many servers you need to meet your anticipated peak concurrent user load. You should add more server capacity to allow for hardware failover or administrative maintenance. The reason for this approach is that one customer may do performance tests with a hardware configuration where they are able to achieve 50 concurrent users with a response time of 10 seconds. Another customer with the same hardware configuration could perform the same tests and determine that to maintain a response time of 5 seconds or less they can't have more than 25 concurrent users. The latter customer will have to buy twice the number of servers to meet their performance requirements. This is why it is important that each customer performs their own performance testing to determine specific hardware needs.
Capture Important Hardware Sizing Parameters
To effectively size your ClearQuest Web Application deployment, the following questions should be answered:
Load Model
Here is an example of how to define the average and peak performance requirements for a ClearQuest Web deployment.
Example Load Calculation
Here is an example of how to calculate average and peak transaction rates.
User population 1500 users
User profiles Sessions/day Transactions/session
Heavy users 20% 12 10
Light users 80% 2 6
% active per day 90% of Heavy users; 70% of Light users
Work Day 9 hours (all activity evenly distributed)
User session is 20 minutes
User Sessions per day is 4,920 =
Heavy users 1500 users*20%*12 sessions/day * 90% Active
Light users 1500 users*80%* 2 sessions/day * 70% Active
Transactions per day is 42,480 =
Heavy users 1500 users*20%*12 sessions/day * 90% Active * 10 Transactions/session
Light users 1500 users*80%* 2 sessions/day * 70% Active * 6 Transactions/session
Concurrent users is 182 = (20 * 4,920) / (9 * 60)
Transactions per second 1.31 = (42,480 / 9 hr) * 1hr/60min*1min/60sec
Concurrent users
is 300 = 1500 / 5
Transactions per second 2.16 TPS = 300*(1.31/182)
Create and Execute Performance Tests
Based on the ClearQuest Web user requirements and sizing parameters, create a set of performance tests that reflect your environment. Start by configuring a group of ClearQuest Web Application and Request Manager Servers. Establish your monitoring tools and confirm that your testing environment reflects your production deployment environment. Then notify your web server, ClearQuest Server, and database server administrators that you will be executing performance tests. Have them monitor their servers during the performance tests. Gradually add ClearQuest Web user load at a consistent rate (such as one user per minute) and record key performance metrics at consistent time intervals. These include:
Determine Bottlenecks and Tune ClearQuest Components
After executing the performance tests, review the monitoring data to determine which processes become resource constrained. For each such process determine what configuration parameters could improve performance (based on the tuning parameters outlined in the tuning section of this document). Adjust these parameters and execute performance tests again. During this process, you should:


text:
Discover a lot more new sufferers on the net by focusing your audiology marketing and advertising on digital approaches from AuDSEO. Nice write-up.. congratulations.. I have been looking for expertise to get Search engine marketing optimised for images.. this article is going to aid me a lot. When you list your organization in high targeted traffic enterprise directory sites, you are putting your organization in front of people browsing for services and items just your like yours.
So most of the Search engine optimization concerned internet developers never prefer to code a web site by means of PHP or ASP. Yet another fantastic way to get your web site identified on the search engine benefits page is to avail a 'Pay Per Click' (PPC) system. In addition, you will need some Search engine marketing computer software tools that may possibly appear very cost-effective at a 1st glance, but they are pricey if you calculate the costs.
Twitter – Twitter accounts are wonderful for Search engine optimisation as Google ranks them highly and they usually come up in page one particular of any search for a company, you have the added added of becoming capable to spam far more on twitter, you will shed fans on Facebook for posting also significantly but you can simply post 1-2 tweets per day on Twitter with out anyone batting an eyelid.
I am thrilled to do organization with a firm exemplifying such buyer service capabilities as yours. When it comes to nearby Search engine optimization updates in 2017, the right key phrases can still make or break your campaign. If your site had the greatest density of the user's essential search term, that was what rated highest on the search engine results web page.
Last month I earned $two.28. Of course, I gave up writing hubs here and keep flitting around among trying to market my small children's book, producing new on the web learning games and auditory apps, and fixing up the educational software and games website we had because the 90's – so lots of stuff for absolutely no income.

subset: commoncrawl


text:
Ballathie House Hotel
Tel: +44 (0)1250 883268
Welcome to Ballathie Country House Hotel in Scotland.
At Ballathie House Hotel, we pride ourselves on our long history of looking after people. Royalty and leading lights of their day have all been entertained in our Scottish country house and on our extensive estate near Perth, Scotland.
These days, Ballathie House's quiet seclusion makes us popular with conference organisers and meeting planners. Sports lovers actively seek Ballathie out as their Perthshire base for golfing, fishing and outdoor breaks. And our country setting is picture perfect for that extra special wedding venue.
Ballathie House Hotel is located on its own Perthshire estate and offers 41 bedrooms, combining luxury scottish accommodation in the Main House and Riverside Building. Each room is individually decorated and elegantly furnished to the highest standards.
All rooms are appointed with private bathrooms, bathrobes and toiletries, trouser press, hairdryer, FreeView TV, direct dial telephones and tea/coffee making facilities. Room service is also available.
Ballathie also offers '3 star lodge' graded accommodation on the Estate at our recently rebuilt Sportsman's Lodge.


text:
We zien dat u de website vanuit Nederland bezoekt. Wilt u de website in het Nederlands bekijken?
Hit enter to search
Before I start - a disclaimer: I may state this and that - Angular is good or bad, Angular pipes suck, I may say Vuejs is not good or it rocks in simplicity but you have to take into account this was written by a person who comes from a .NET background, working in PHP nowadays and has solid JavaScript background. In total, I've been a developer for more than 10 years. I played with these frameworks for 10 days, redoing a task I will explain below. The conclusions are mine and represent my opinion alone.
So I got a task to create control panel for CastIt using new JavaScript frameworks. This was an internal task, planned as a sort of a test for 2 frameworks (Angular & Vue.js).
But what is CastIt? It's a narrowcasting & digital signage platform, that outgrew it's initial purpose by also having touch applications, connections to hundreds of apps and loads of analytics in it. You can read more about it here, I will skip the intro and jump to the part I was involved in for the sake of explaining the comparison of the JavaScript libraries.
In CastIt there are multiple channels you can control, with multiple players running even the same channel. You need a way to monitor all of this activity and that is what I was aiming to rebuild with the task. The control panel was already built using react. Great. What else? CastIt is mainly built in PHP but the part I am calling and pinging for information is node.js.
So I started with Angular 4, which I will refer as it is called - Angular. Now, a little intro about Angular. Its main purpose is to build SPA apps, unlike Vuejs which can be used for SPA but also for different application types. Soon, I realized it's not enough to go through the official Angular documentation.
There is much more you need to learn in order to get started. After some reading I decided to move and change the development environment. I started using Visual Studio Code as the new development environment. There are many reasons for doing that. Its lighter, much faster and it has great TypeScript and Git support. Using Angular with VS Code required additional effort and learning. I had to install and learn a bit about Node.js, to use NPM, Webpack. First, you need to install Node.js and NPM. You also need Webpack – a module bundler which simplifies your work tremendously. Without it, it would be pure hell. So I started with Angular command line interface (cli) as the Angular documentation suggested and installed a new application, which in turn gave me a template that included built-in support for TypeScript, Webpack, Unit tests. TypeScript support seemed natural.
As for unit tests, template had the Karma and Jasmine unit tests preset. Unit tests launch in chrome browser, with visual feedback for each test. So it was very useful and convenient to use. Visual Studio Code offers autocompletion, F12, "ctrl + ." support which is Visual Studio like. So, that's really cool. And what is best, after a while or better said right from the start, I realized TypeScript has many similarities with .NET object oriented programming, which I found to be a great feature. Its type safe and I find that as an important benefit (because of my .NET background). You can make and use interfaces, you have constructors. Another thing that I noticed was code separation, that is, the Angular template initial setup structures files in a way that it separates html, css and TypeScript. I find that as a big plus as you keep away business logic from the html/css part, which should not be concerned of it.
Modularity is one of major Angular features. When coding with Angular, it is all about organizing code into the buckets. Angular also introduces services, which are placed where you can write reusable business logic, extract and encapsulate unique repeatable functionality. Also it is notable that Angular strongly relies on dependency injection. It is implemented in a simple way, which is nice. Another benefit of all modularity, components and services is that, in terms of coding styles, Angular guides the developer how and where to write code.
To sum it up, all the concepts seem nice but along the way I realized official support documentation is not that good. It lacks a lot of stuff, and does not cover all the areas. Actually, I realized that Angular 4 in general lacks articles and documentation all over the internet. This is partly because at the time I was working with it, it was rather new as it was officially released in April 2017 and I was working on it around August 2017. Partly it is because old Angular JavaScript was very popular too. But there we come to the point where I realized also that Angular 4, as a successor to Angular 2, probably also lacks documentation because of the number of breaking changes introduced in a rather short period. And it's not easy to keep up with breaking changes that occur every now and then. Well, because of that and it's outright complexity, it takes some time to learn it, so be prepared. There are also a lot of important libraries that one should learn about. Essential ones are RxJS, NgZone, Routing, NgRx for state management. In the end, the result of the CP (CP4) implementation with Angular was that initially it took some time to startup, but apart from that it ran smoothly. Overall impression was that latest Angular is pretty cool.
Some notes and ramblings. To reflect on Angular complexity. For example, animations do not seem like a great implementation by Angular – code syntax and results were way too difficult compared to yielded results – so in the end I abandoned using Angular animations. The situation is similar with pipes. Pipes are used to manipulate and transform data. Pretty weird term for what is usually called filtering. Actually it takes in data as input and transforms it to a desired output. In my case I needed channels table to be able to be sortable. Should not be complex, right?
No. So Angular uses pipes and for me that concept was kind of weird. It was like a separate piece that will not fit into the puzzle at all. Another note that adds to confusion is that Angular documentation suggest to use impure pipes with great care. If pipe is set as impure then they track changes and can easily leave an impact on the user experience, so be careful when you use it. It's like, why have it simple when you can make it complex.
The syntax is also kinda inconsistent, you can write the same thing in several different ways. But make only one miss and it will not work, without any warnings. For example with pipes, arguments are separated with colons? Don't know why. Syntax to do two way binding was unusual as well or transferring event data from one component to another parent/child component is not that natural as well. In the end I can't escape the feeling that learning curve for Angular is just too steep and not backed up with enough docs. So it seems like too much of an effort at the end or better said an undocumented unfinished product (at the time of writing blog post).
Then vue came along. It relies on a component based approach too. That is a plus and in that sense it's similar to Angular. But unlike Angular it does not have code separation, instead JavaScript and html by default reside in the same file with vue extension. One of the first impressions I got was that it is much more "pure" JavaScript compared to Angular. Vue support docs are much better. In fact, it's better then Angular by a huge margin. In terms of complexity it seems much simpler than Angular, although Angular has a lot more object oriented approach which initially I liked more.
Regarding the syntax, some parts are pretty similar to Angular. I am referring to template syntax like v-for and *ngFor or v-if and *ngIf. One note though - Angular syntax is case sensitive. But there are some special cases with vue as well, like with html attributes, where camelCase property names are using its kebab-case html equivalent. Note, however, that I spent no more than 2 weeks working with it so I would not be surprised if I missed many features and details and that many of them have their alternatives. It's only that I did not have enough time to learn about them. For example, later I discovered that there is a vue template that adds support for TypeScript. That said, it means that the same object oriented feeling I got with Angular, can be achieved with vue using that template.
Still we can say TypeScript is not there by default, so small advantage for Angular (in case you are into TypeScript as I am). I mean, TypeScript is not a 1st class citizen in vue. My final impression is still that Angular is more modular than vue. I also learned that, while Angular has all the functionalities you need within its framework, routing, state management, http, its validation, animations, … basically has everything under its umbrella, on the other hand, with vue I had to use some additional 3rd party libraries. For example, you don't have built-in http/ajax support. Instead axios library is suggested as a 3rd party implementation. Even though it looks cool that you have it all when using Angular I could not find many downsides because of it. I can imagine it may cause some breaking changes over the time but Angular was prone to breaking changes within its sole framework too.
Well, even though it was a positive experience while working with vue in general, there are some things which I normally did not like. For example, at least on first try, a vue project template uses mocha, karma and phantomjs as a browser for unit testing. And using phantomjs as a browser is not as nearly convenient as it is the case with the default Angular setup. Also debugging and stepping through the code in console did not work well too. For example, setting a breakpoint would not work for some specific lines. It seems it is related to source-map setting, but I was unable to resolve it in the short time I had available.
Which is the chosen one? On one side you have Angular backed up by Google. Still vuejs seems lighter and faster, not supported by giants but still has some notable implementations like for wizzair, euronews, alibaba, baidu, facebook newsfeed. Later I found out that vue is supported by the Chinese retail giant Alibaba. Still, because Angular is powered by Google it has bigger influence on the job market. So if you consider to sell your expertise as a developer, Angular might be better option at the moment of writing this.
But as vue's popularity is growing fast, it should be considered as real contender and a viable alternative in the future. While the current popularity on the market might be on Angular side, in case of building new applications, all the signs imply to use vue rather than Angular. In the end there is another important conclusion. There are number of new frameworks lately and they do update at such rapid pace that it's hard to be up to date all the time. What is essential is to fundamentally learn JavaScript. That is the real knowledge which is the foundation of any new framework. Frameworks come and go. Knowing them is a +, truly knowing JavaScript is a true value, ++.
published 2 years ago


text:
Three Crosses
There were three of us standing tall and proud.
We felt the heat from the sun above
How could this be we thought as the day drew to a close?
A woman cried! "What have you done to my son?"
"Lord remember me one man whispered low.
We stood like a cross hurt to our core.
We soaked up the blood that was shed for all.
Man now overcome's satan by the word of his testimony and the Blood of the Son.
Written by Sybil Shearin June 2007
© Designer Lady
"Converging Shadows"
© by Bruce DeBoer


text:
Provisional Status
Students with bachelor's degrees from accredited institutions whose scholastic records are below the standards for admission to full graduate standing may be admitted provisionally when unavoidable, extenuating circumstances affected their undergraduate averages or when progressive improvement in their undergraduate work warrants provisional admission. Students admitted provisionally under these circumstances can attain full graduate standing after completion of nine or more graduate credit hours with a minimum GPA of 3.000. Courses taken for S/U grade cannot be used as part of the minimum.
Provisional admission may be granted to applicants with bachelor's degrees from accredited institutions who lack undergraduate work considered essential for graduate study in a major field. Applicants with bachelor's degrees from non-accredited institutions may be granted provisional admission when their academic records warrant this status.
Full graduate standing is granted when the deficiencies responsible for the provisional status are corrected through additional course work (without graduate credit), provided the student has maintained a satisfactory academic record (3.000 GPA) on all course work taken in a graduate classification. A change from provisional status to full graduate standing is effected only upon the recommendation of the department in which the student is seeking the degree.
A graduate student is not eligible for appointment to an assistantship or fellowship while on provisional status.


text:
item(s) in your cart
Have you seen our latest products?
Large hedge shears with long wooden handles of 50 cm, and a large razor-sharp blade of 200 mm. The long handles give you a great reach, so cutting up to 2.5 metres is possible. You can also cut large surfaces faster, easily penetrate deep into the crop, and effortlessly cut lower without bending.
Total length: 780 mm, Handle length: 500 mm, Blade length: 200 mm
Weight: 1050 g
Join our mailing list to get plant tips,discounts and news delivered to your inbox.Don't miss out!
Southern Woods Plant Nursery
Main South Road, Templeton
Christchurch, New Zealand
Freephone 0800 800 352


text:
720 articles since October 18 2012.
Welcome to the Stardew Valley wiki, started for the game developed by ConcernedApe!
It's up to you to choose your path...grow your field into a farm, raise livestock, improve your skills and become a part of the community, finding love and friendship! Fish, explore caves, renovate your house, decorate, and drink Joja Cola!
Before you start editing, we ask that you please take a look at our editing policy to make sure you get the most out of your experience here!
|Wiki Activity
Haley is a character and one of the six bachelorettes in Stardew Valley. She loves taking photos with her camera and keeping up to date with all the latest fashion trends. Read more >>
| To write a new article, just enter the title in the box below.
Community content is available under CC-BY-SA unless otherwise noted.


text:
Chekov does rural Pennsylvania in the latest play performed by Between Shifts Theatre Company.
Vanya and Sonia and Masha and Spike is a Tony Award-winning Broadway farce by playwright Christopher Durang.
"It's really, really funny, but it has also got great, touching moments in the show. I look at it as an absurd family comedy," says the play's director, Michael Hewitt.
"It's about the way siblings behave when they are reunited. There's a lot of deep stuff that the three siblings — Vanya, Sonya and Masha — go through. Spike tags along as Masha's toy boy."
Between Shifts has embraced the farce as a form it regularly turns to for productions; it has proved a popular choice with audiences.
"Comedy seems to work very well in Squamish and the Sea to Sky. I think it's a dark world sometimes and everybody just needs a laugh," Hewitt says.
"People feel more faith going out and watching something that they know will not make them melt down or anything.
"I gravitate towards comedies and it shows in the ticket sales."
In the story, adult siblings Vanya and Sonya live in the family home, mourning lost dreams and missed opportunities. When their Cassandra-like maid warns of doom and their movie-star sister Masha turns up with her young boyfriend, the family reverts to their old ways.
The aim of Durang as playwright, says Hewitt, is to blend Russian great Anton Chekov's ennui with modern hang-ups.
"We do the deeper stuff, of course, we did The Glass Menagerie a while ago and we did Art, which was a comedy with serious undertones, and we're doing a great play in the season coming up called Kayak. A very interesting piece," he says.
"The company hangs on to those dramas. But it's good to start the season off with this show, a parody."
The cast includes Rod Neufeld as Vanya, Kathy Daniels as Sonia, Carla Fuhre as Mash and Todd Weitzel as Spike.
"There is a lot to be said about community theatre. I like to think that we bring to the table work that is just as good as some of the equity productions in and around the big city," says Hewitt.
"I do professional work in Vancouver as well, and I can tell you that Between Shifts brings quite a professional version of Canadian theatre."
As well as the cast, local people have supported the production behind stage, including Producer Christine Gavin-Bartlett, Production Stage Manager Tea Stefiuk, Costume Designer Christa Duttchen, Composer Darrell Booth, Props manager Barbara Stover, and Scenic Lead Carpenter Christopher French.
The play runs from Thursday, Oct. 6 to 8, and from Oct. 12 to 15. Tickets range from $10 to $20 and are available online at www.betweenshiftstheatre.com, or in person in Squamish at Billie's Flowers or InBiz.
May 27, 2020, 4:40 PM
Doctors credit fast response by officials, people's curve-flattening actions More...
May 27, 2020, 4:04 PM
The number of people in B.C. battling COVID-19 is down 14, to 244, in the past 24 hours More...
May 27, 2020, 3:51 PM
Francis Masculino plans to use his winnings to pay off his vehicle, purchase a home and spend more time with his family More...
Interactive Map
Click each province to see the number of confirmed COVID-19 cases, deaths, recovered patients, and tests administered...more.


text:
90% of American grown-ups possess a mobile phone, with 29 percent of cell proprietors conceding their telephone is "something they can't envision living without." With more shoppers disposing of landline telephone benefit, remaining associated with the world through a cell phone is turning into a need.
So when a house or a flat doesn't have capable and predictable remote association, it can affect and baffle your purchasers' everyday lives. Be that as it may, would it be able to be a land bargain executioner?
"A solid cell gathering is an essential," Michael Graves, a partner agent at Douglas Elliman as of late told the New York Times. At a current private flat appearing, he saw more potential purchasers focusing on the quantity of bars on their mobile phones, showing that solid cell gathering was critical to them. "In case you're living in Manhattan, you shouldn't get the phone gathering that you would in the forested areas, particularly when you're purchasing a multi million-dollar condo."
In condo structures and tall structures all through the nation, the battle for tolerable remote administration is genuine, and tenants and purchasers are taking load of a posting's cell benefit before they make an offer. Angela Huffman, a leaseholder in Manhattan said she "checked the mobile phone gathering at each place she visited amid a flat chasing visit this late spring." After going by a couple of postings, she at last picked a loft where the remote administration was the most grounded. "It unquestionably had an impact in my choice," says Huffman. "On the off chance that one of them didn't have mobile phone benefit, that would have been a no for me."
Remote issues originate from the components of the building: thick solid dividers, fortified steel floors and extraordinarily covered low-outflows windowpanes are a shrewd triumvirate for meddling with PDA signals. Add to that the likelihood that the building is taller than cell towers and may have meddling remote signs and occupants may discover they are dropping a greater number of brings in their urban family room than they may on a rustic excursion.
Keeping in mind the end goal to amp up remote administration, designers and property directors can work in-house systems called circulated receiving wire frameworks into their properties. They utilize fiber associations with divert the flag radiated by system suppliers into the structures themselves. Reception antennas are covered up all through each floor under smoke caution estimated covers. These frameworks are regular in other business structures and are turning into the standard in new private activities. They not just lift remote signs, they additionally make it less demanding for some individuals to utilize the remote system in the meantime.
"The discussion used to be along the lines of, 'Tune in, you may have the capacity to expand values by doing this,' " says Angela Ferrara, the official VP of offers and renting at the Marketing Firm, an advancement, renting and advertising organization. "Presently, it's 'You have to do this keeping in mind the end goal to be focused.' "


text:
Iran is ready to join the World Trade Organization (WTO), Iran's Minister of Industry, Mines and Trade Mohammad Reza Nematzadeh said on Wednesday.
He made the remarks in a meeting with the Finnish Minister for Foreign Trade and Development Lenita Toivakka on the sidelines of WTO's Tenth Ministerial Conference in Nairobi.
In the post-nuclear deal situation, Iran is ready to pursue joining the WTO, the official said.
Nematzadeh referred to the positive outcomes of nuclear deal between Iran and P5+1, adding that the ground is ready for enhance of all out ties between Iran and Finland.
He urged all WTO members including Finland to support Iran's membership in the international body.
Iran is ready to kick off negotiations for joining the WTO, trade minister noted.
Nematzadeh said that Iran is ready to cooperate with Finland in fields of economy, industry and new energies.
He said that Iran is keen to boost cooperation with the European Union and voiced hope that after removal of sanctions in the near future, Iran can promote ties with the world.
WTO members were urged at the opening session of the WTO's Tenth Ministerial Conference in Nairobi on 15 December to crown a successful year of multilateral diplomacy by delivering on a package of trade deals that would benefit the world's poorest and spur global economic growth.
Kenya hosted the first WTO ministerial conference on African soil. The meeting comes more than 20 years after the conclusion of the Marrakesh Agreement in Morocco which led to the creation of the WTO in January 1995.


text:
The openEHR Foundation is pleased to announce Release 1.0.2 of the specifications. In what appears to be a strong sign of stability, only 15 Change Requests were needed, of which only 7 had any effect on the formal specifications, and no impact on existing schemas or data.
Thanks to everyone in the community who contributed to this release.
Other resources: Release 1.0.2 home page, release notes
Specifications Quick Links
Clinical Models Quick Links
Resources Learn More


text:
Portwest Cs12 Coldstore Coverall
Manufacturer: Portwest
Product code: CS12
- EN342, cold protection.
- Back elasticated waist.
- Knitted cuffs with thumb holes.
- CE certified.
- Fleece lined collar.
- ID Card holder.
- Phone pocket.
- Pack-away hood.
- Radio loop.
- Reflective tape.
- Oxford weave.
- Stain resistant fabric.
- Fabric: 100% Breathable polyester.
- Lining:100% Polyester.
- Wadding: 100% Polyester filling.
- Breathable
- Breathable fabric allowing free circulation of vapour and heat
- Knee Pad Pouch
- Product contains Knee Pad Pouches allowing kneepads to be inserted to protect the workers knees.
- Thermal Properties
- Product contains thermal properties
We offer Free Delivery on all orders over a particular amount depending on your location, details are provided at the checkout.
Non-personalised items: 3 to 5 days within the UK, 5 to 10 days worldwide.
Personalised items: 7 to 10 days worldwide from artwork and order acknowledgement sign off.
Orders are sent via courier (Interlink, DHL or FedEx) and a signature is required upon delivery.
We offer a 30 day money back guarantee on all non-personalised items and returns of faulty items are free of charge.
Please Note: You are required to cover any carriage costs when returning none faulty items for exchange or refund.
For more information please view our returns policy
Not the portwest trouser you were looking for? View more portwest trousers or our entire range of portwest workwear.


text:
Two reasons you should attend an online college in your own state
I think we would all agree that attending college online is more convenient than attending traditional classes. But at what cost? Well, it depends… Do you plan on attending a for-profit college such as Kaplan, or a traditional institution such as the University of Illinois?
If cost of tuition is an important consideration, you may want to take a look at well-established, traditional colleges in your own state. Not only can you take advantage of in-state tuition rates, but you won't be raising eyebrows when your resume shows you working in California and attending college in Florida.
If you are interested in Online Colleges in Canada, visit my Canadian Online Degrees post.
Online colleges by state
- Alabama
- Alaska
- Arizona
- Arkansas
- California
- Colorado
- Connecticut
- Delaware
- District of Columbia
- Florida
- Georgia
- Hawaii
- Idaho
- Illinois
- Indiana
- Iowa
- Kansas
- Kentucky
- Louisiana
- Maine
- Maryland
- Massachusetts
- Michigan
- Minnesota
- Mississippi
- Missouri
- Montana
- Nebraska
- Nevada
- New Hampshire
- New Jersey
- New Mexico
- New York
- North Carolina
- North Dakota
- Ohio
- Oklahoma
- Oregon
- Pennsylvania
- Rhode Island
- South Carolina
- Tennessee
- Texas
- Utah
- Vermont
- Virginia
- Washington
- West Virginia
- Wisconsin
- Wyoming
You may also want to perform an online degree search to identify colleges and universities that meet your needs.
Related posts:
- 5 tips for selecting an online university
- Traditional colleges vs. Online colleges
- What jobs best suit your personality? Take an assessment quiz!
- Care to test drive an online course?
- Five ways to spot a diploma mill
- Why you should consider taking online classes
- Is online learning right for you?
- Importance of online college accreditation
- How online degrees affect your financial aid eligibility
Top Online College Degree Programs


text:
Simply put, microblading is transformative . . .
Obviously, we don't live in a perfect world. If we did, everyone would have naturally perfect eyebrows. As nice as that dream sounds, naturally perfect eyebrows are about as common as winning the lottery!
The truth is, all eyebrows are not created equal! Some brows require little effort to look perfect while others require the help of a trained professional. Here at b.LUXE we have the answer to your eyebrow woes with microblading! This technique transforms your brows, giving the appearance of natural shape and fullness.
Eyebrow microblading goes by a few different names like microstroking, micropigmentation, eyebrow embroidery and 3D eyebrows. No matter the name, the procedure of microblading eyebrows is relatively new here in the United States, while it has been popular in Asia and Europe for roughly 25 years. That's actually not a bad thing because it has allowed the techniques to refine and improve significantly since its origin.
The procedure sounds a lot like a tattoo because that's exactly what it is! More specifically, though, microblading is a semi-permanent eyebrow tattoo that uses fine, pigmented strokes to simulate natural hair growth. These are nothing like the permanently tattooed eyebrows of yesteryear that look like they were drawn on using a sharpie, then fading to unnatural shades of blue and green. This is where the refined skills of the modern microblading artist come in to play!
There are two major differences that make today's microblading results more aesthetically pleasing when compared to the results of previous permanent cosmetics.
First, the type of pigment used for modern microblading is iron-oxide based. Iron oxide has been a popular ingredient in cosmetics like foundation, blush, lipstick, and eyeshadow for decades. An iron oxide base allows the color to softly fade over time and ultimately vanish, unlike the inks used in permanent cosmetic tattoos.
Second, the pigment used for microblading isn't implanted into the skin as deeply as the depth used for permanent cosmetic procedures. The proper depth for the color to be implanted during the mircoblading procedure is the upper layer of the dermis. The pigment being implanted to the correct depth, combined with its iron oxide base is what gives microblading results the appearance of natural looking eyebrows. The semi-permanent qualities of the microblading pigment prevent it from fading into unnatural shades that are so common with permanent cosmetics.
Not only do microblading results look amazingly natural, they require no daily upkeep! So kiss the daily eyebrow routine goodbye!
No love loss here when saying, "see ya later" to your daily eyebrow routine! Microbladed eyebrows typically last somewhere between one to three years, depending on the client's skin type and lifestyle. We recommend a touch up 12-18 months later to keep the color looking vibrant, and the microblade strokes crisp.
Another added benefit of semi-permanent makeup is its flexibility! Considering how skin changes with age and eyebrow trends can differ with time, the eyebrow shape and color can be adapted to fit changes in skin and current eyebrow trends!
You are one step away from your face-flattering, eyebrow transformation!


text:
|Bioconversion of Organic Residues for Rural Communities (UNU, 1979)
|Production of single-cell protein from cellulose
I am indebted to several of my collaborators for their excellent assistance, especially Mrs. Margaret Bumm, Mr. T.F. Miller, Mr. Richard J. Summers, and Mr. M.S. Alam (FAO Fellow) during these investigations. Partial financial support for recent investigations was provided by a grant from Southdown Sugars, Inc., Houma, Louisiana, USA, obtained through Louisiana State University Foundation, Baton Rouge.