The default port that the OC4J HTTP server listens on is configured in the $ORACLE_J2EE_HOME/config/defaut-web-site.xml file. The port number used for the HTTP server is specified as an attribute of the <web-site> tag.

The default HTTP port of OC4J standalone is 8888. This is specified in the configuration file <J2EE_HOME>/config/http-web-site.xml. If you have installed one of the Oracle Application Server distributions instead of OC4J standalone, then you must access Web applications deployed on OC4J via Oracle HTTP Server. The default port of Oracle HTTP Server is 7777.

The port used by the OC4J HTTP listener is defined in the configuration file <J2EE_HOME>/config/http-web-site.xml file using the port attribute of the web-site tag. lt;web-site port="8888" display-name="Oracle Application Server Containers for J2EE HTTP Web Site">

Remote Method Invocation (RMI) in enables developers to build distributed applications in java. However RMI calls are normally blocked by firewalls. RMI HTTP tunneling is a RMI implementation to provide a way for RMI to get through firewalls using HTTP. Your global-web-application.xml should have this entry: <servlet> <servlet-name>rmi</servlet-name> <servlet-class>com.evermind.server.rmi.

Before you run the configure script, simply set the CACHE_HTTP_PORT environment variable. setenv CACHE_HTTP_PORT 8080 ./configure make make install

Connect to the router through web browser. Set the broadcasting IP address and Port, select TCP-IP protocol. How to ... If you hear nothing from your broadcasting page, check the 'Tools > Internet Options > Advanced > Java (Sun) > Use JRE v1.x.x_xx for <applet>' option in MS Explorer. If there is no such option or if the JRE version is lower than 1.

OC4J standalone comes with a command line utility, admin.jar. This enables you to perform a set of administrative functions from the command line. Also, you may directly modify the XML configuration files in the OC4J standalone environment.

Please see the relevant OC4J User's Guides (standalone or Oracle Application Server) for more information.

There are two ways. Launch the SwiftMQ explorer, connect to the router and navigate to JMS Swiftlet/Listeners. Select the listener you want to modify,... Why do I get this message when I try to connect to a queue ? javax.jms.InvalidDestinationException: Queue '<queueName>' is not local! Can't create a Consumer on it! There are two reasons why this may happen: The queue is on another router and you try to create a receiver on your local router on that remote queue....

The OC4J HTTP server can be configured to support directory browsing of deployed Web applications. The following steps will enable directory browsing for a deployed Web application. You should now be able to browse any directories that do NOT have a welcome file present. Welcome files are configured in your web.xml file, with the <welcome-file-list> attribute.

The http-port (now renamed as http-admin-port) is, as documentation/userguide tells, the port where Kannel listens for http-administration commands. So it is not linked to your Apache/whatever httpd, it simply uses the same protocol (HTTP). And as Kannel is not run as a 'root' program, this port number must be over 1024. Default is 13000, after which, for example, the status of Kannel can be checked this way: Those markings mean that you have ran into CVS conflict.

You have to define the resource in the deployment descriptor e.g. you are trying to access the URL resource from a web application then you have to have the following entry in the web.xml You have to map the resource name e.g. url/MyURL into a location in your vendor specific deployment descriptor e.g. orion-web.xml as follows: lt;resource-ref-mapping name="url/MyURL" location="http://debu.us.oracle.com" />

You can configure your own default search index in the Preference section, please note that this setting will not apply to all but specific accounts. For information about other personalized settings, please refer to Preference of the Search Guide.

Port trunking is connecting two switches with multiple links that act as one high-bandwidth link. Up to four port (full- or half-duplex) can be used for each trunk on a Switch 2000 or Switch 800t. This enables up to 800 Mbps of bandwidth for linking switches. The benefits of port trunking are: The illustration below shows how port trunking is used in three different locations. Initially, all of the links were 100 Mbps links at 100TX speed and in full duplex mode.

You can find instructions for most popular routers at http://www.portforward.com/routers.htm. Try http://www.canyouseeme.org/ to check your port forwarding.

Yes, you can specify multiple http_port lines in your squid.conf file. Squid attempts to bind() to each port that you specify. Sometimes Squid may not be able to bind to a port, either because of permissions or because the port is already in use. If Squid can bind to at least one port, then it will continue running. If it can not bind to any of the ports, then Squid stops. With version 2.3 and later you can specify IP addresses and port numbers together (see the squid.conf comments).

You can run HTTPS on any port, but the standard specifies port 443, which is where any compliant browser will look by default. You can force your browser to look on a different port by specifying it in the URL like this: https://secure.server.hell:666

If you intend to use Xeena to access DTDs or XML files that reside on external (outside your firewall) servers, you may need to tell Xeena which proxy server to use. This can be done via the InstallShield wizard (Windows only), or thereafter by editing the xeena.bat file (Windows) or the xeena.sh file (Unix) and setting the PROXY_SETTINGS environment variable (by default set to -DproxySet=false) to

Is the server name known to the DNS? Try using an explicit IP address instead of a name (eg. 123.456.78.9:0 instead of snoopy:0).