These instructions assume $WL_HOME is the install directory, and $WL_DOMAIN is the WebLogic domain, found in $WL_HOME/config. $WL_HOME is set by the setEnv command in the $WL_HOME/config/$WL_DOMAIN directory. $WL_DOMAIN is not directly set by the startup and config scripts, but provides an easy shorthand for the WebLogic domain used. Make sure RootCause is enabled in the shell that you start WebLogic. Make sure the app server is stopped.

These instructions assume $IAS_HOME is the install directory of the iPlanet App Server. $IAS_HOME does not have to be set for the application to be run or for RootCause to trace it. It is convenient to have $IAS_HOME set, in addition to $IAS_HOME/bin in your $PATH. IAS_HOME/bin/iascontrol is the command line script that controls starting and stopping of the iAS 6.5 server. Make sure RootCause is enabled in the shell that you start iascontrol. Stop the app server by running 'iascontrol kill'.

Yes, it can. Some hints are provided in the EJB example tutorial and in the WebLogic 6.1 interoperation howto.

These instructions assumes $JBOSS_HOME is the install directory, and $JBOSS_DOMAIN is the domain used, typically found in $JBOSS_HOME/server. Make sure RootCause is enabled in the shell that you start JBoss. Make sure the app server is stopped. Typically the JBoss is started by first calling $JBOSS_HOME/bin/run. Create a new workspace for this JVM, the main class name is "org.jboss.Main". You can add the "J2EE Server Directory" in the "New Workspace" dialog.

The Verity application runs as a Web-App on Weblogic. Adding the Verity vindex and vsearch jars (and all other jars) to the WEB-INF/lib directory (the directory for a webapp) corrects the problem. Add the jar files to the CLASSPATH through the command line. Background: WebLogic sets the URLStreamHandlerFactory on the URL class.

www.bea.com/products/weblogic/server/index.shtml and www.weblogic.com/docs51/admindocs/apache_bridge.html.

It is an Apache module called "mod_wl" that creates a handler that forwards requests to the BEA Weblogic application server.

The first thing we need to do is check that you are running one of the JVMs that RootCause supports. Websphere ships with it's own version of the JVM and so long as this is a Sun JVM, RC will work for the tracing components. If it's an IBM JVM, that's only supported on AIX. To see this, open an X terminal or some other console on the machine that you have Websphere running on.

Go to the "Java and JVM" of Server Settings, http://yourhost:8500/CFIDE/administrator/settings/jvm.cfm page, and enter the full path, C:/CFusionMX/wwwroot/WEB-INF/classes/DBF_JDBC30.jar, in the Class Path. Then, click "Submit Changes". Please go back to the administrator page, and go to the "Data Sources" of Data & Services, http://yourhost:8500/CFIDE/administrator/datasources/index.

xTier™ as a product does not compete with BEA WebLogic or any other application server vendors. From the beginning, xTier™ was designed to bring additional value to existing infrastructures by providing a host of unique services in cross-paradigm manner. In other words, xTier™ and J2EE are entirely complementary to each other. xTier™ is not a test automation technology and therefore it brings an indirect value for reducing allocated time (cost) to the testing phase.

Start the Active Directory Sites and Services Manager (Start - Programs - Administrative Tools - Active Directory Sites and Services Manager)

The DHCP Server Service is configured using "DHCP Manager" that is installed after the installation of the DHCP Server Service. Exclusion - start and end, e.g. 200.200.200.20 and 200.200.200.30, would mean available addresses would 200.200.200.10-200.200.200.20 and 200.200.200.30-200.200.200.100 A message that the Scope has been added, but is not active, would you like it to be active, click Yes.

A list of valid parameter names for the Session Descriptor in webLogic 6.1 are as follows: CacheSize ConsoleMainAttribute CookieComment CookieD...

Yes. A Solaris PC PC NetLink system can be a member server that provides file and print server functionality without using any of its resources for authentication duties (which belong to PDCs and BDCs).

This depends almost entirely on what you do with it. If you trace almost nothing, it will introduce almost no overhead. If you trace every method call on your machine, it will slow things down too much. The keys to good performance are: only ask questions you want the answers to; that is, don't blindly trace everything if you're worried about performance; and avoid logging data over the network: put your workspace on a local disk.

This PhotoVu Technical Support FAQ is provided as information only. PhotoVu does not recommend or give advice on any network or security settings. If you decide to use this information, you do so at your own discretion. By changing ANY network setting, you can introduce security risks. Please understand what these are within your own environment before making any changes.

About SyncEx | Company | Top 10 Reasons | Partners | News | Live Demo | Free Download | Purchase | Testimonials