confguring auto vue servlet on weblogic

If the AutoVue server will be accessed by clients outside a firewall, direct access non-standard ports (i.e. non-HTTP) are often blocked. To enable clients to access servers that are protected by firewalls, a servlet is provided to tunnel requests through the HTTP or HTTPS protocol. When tunneling is required, the AutoVue client encodes requests from the HTTP/HTTPS protocol and attempts to invoke the servlet on the specified server. The servlet decodes the parameters included in the request and forwards the request to the AutoVue server using a socket connection. The servlet also replies to the client machine using the same HTTP/HTTPS protocol.

Two changes are needed to configure the server.

A) Install the file vueservlet.jar into the Application server or Servlet engine. Follow the instructions provided with the Application server or Servlet engine.

Tunneling through J2EE-enabled Application Servers This section provides instructions for creating and deploying VueServlet for J2EE application servers. Creating a WAR File for VueServlet Complete the following instructions to create a WAR file for VueServlet. 1 Create a directory. Example: C:\csiwar 2 In the folder C:\csiwar, create a sub-directory WEB-INF. 3 In WEB-INF, create a directory lib: C:\csiwar\WEB-INF\lib 4 Copy vueservlet.jar to C:\csiwar\WEB-INF\lib. 5 Create a deployment descriptor. The deployment descriptor should be stored as a file named web.xml in the WEB-INF directory. • The following is the mandatory header for the web.xml document. It defines the document as an XML file and relates the file syntax to the DOCTYPE resource specified.

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
Application 2.2//EN" "">

• Use the following code to specify the deployment descriptor needed to deploy the VueServlet.


The <servlet-name> parameter is how the Servlet is known within the XML file.

The <servlet-class> parameter is the fully qualified Java programming language class name of the Servlet. The <url-pattern> parameter is how the Servlet is referenced from a Universal Resource Indicator (URI).

Update hostname with the name of AutoVue server machine.

Note The parameter structure must follow the order in the DTD definition. For example, all <servlet>s must be defined before any <servlet-mapping>s can be specified. • Update hostname in web.xml with the name of AutoVue server machine.

6. To create the WAR file, use the “jar” utility from the JavaTM Development Kit distribution. If you are in the root directory you created for the WAR contents (C:\csiwar), use the following command: jar cvf VueServlet.war WEB-INF Now you can deploy VueServlet.war using any J2EE compliant application server or Web container.

7 After the VueServlet is deployed, to access the content, type the following into your web browser:


The <context> parameter can be set in the deployment phase or set automatically by the application server. Some application servers allow you to specify the context name, but generally the WAR file name is used as the context.

Steps to Deploy the WAR File 1 Launch the administrative console of your application server. 2 Select Install a new Web application. 3 Browse and select VueServlet.war. 4 Specify VueServlet for the context name. 5 Deploy VueServlet.war.

B) Update the Web pages that embed the AutoVue client to include the full URL of the Servlet (something like http://servername/servlet/VueServlet) as the JVUESERVER parameter.

The VueServlet supports two parameters: the JVueServer parameter and the Verbose parameter. The JVueServer parameter needs to be set to the hostname:port value used when starting the AutoVue server. By default, localhost:5099 is used and will work if you installed the AutoVue server on the same machine as the Web server.

You can specify more than one hostname:port separated by semi-colons ( ; ) for fail-over. In other words, if one machine is down the servlet will try the next machine. The Verbose parameter enables verbose output. Both parameters are optional. If JVueServer is not specified, it defaults to localhost:5099. The servlet assumes that AutoVue server is running on the same machine as the Web server and communicates through port 5099. If Verbose not specified, it defaults to False.

How to deploy application to weblogic application server 10.3g

Deploying the application to Weblogic Application Server

The deployment procedures below are for using Weblogic 9.1. The procedures for using different versions may vary.

In Manager, locate the existing Web application on the Applications page.

  1. Check the box next to the Web application you want to deploy to Tomcat and hit the ‘Export’ button.
  2. In the File Download dialog that appears, click the Save button.
  3. In the ‘Save as type:’ section, choose All Files.
  4. The default file name extension will be .zip. Change this to .war and save it to the file system. Click the ‘Close’ button when Save is complete.(For example: C:\temp\myapp.war)
  5. Start Weblogic Server. a browser will open to http://localhost:7001/index.jsp. Click the ‘Start the Administration Console’ button to open the Administration Console.
  6. In the Change Center section of the console, click the ‘Lock and Edit’ button to open the server instance for changes.
  7. In the Domain Structure section of the console, find the ‘Deployments’ link and click on it.
  8. You will see a Summary of Deployments. Here is where you will deploy the war file. Find and click the ‘Install’ button.
  9. Browse to the location on your file system where the .war file was saved. Click the radio button next to the .war file and click ‘Next’
  10. You want to deploy this module as an application. For the targeting style, make sure ‘Install this deployment as an application’ is selected. Click ‘Next’.
  11. Click ‘Next’ again to accept the defaults in this next pane, then click ‘Finish’.
  12. You will now get a summary list of the settings for the deployment. Click the ‘Save’ button. If everything went ok, you will see a message in green that says ‘Settings updated successfully.’
  13. Back in the Change Center section of the console, click the green ‘Activate Changes’ button. The application has been ‘prepared’, but not yet deployed at this point.
  14. Back in the Domain Structure section of the concole, find and click on the ‘Deployments’ link. In the Summary of Deployments, find your application, check the box next to it and click the ‘Start’ button. Select ‘Servicing all requests’. Click Yes to continue
  15. If the state of your deployment says ‘Active’, you have successfully deployed your Web application to Weblogic.

Testing your deployment from within the Weblogic Administration Console

You can test your application from within the Administrative Console by following the steps below:

  1. In the Domain Structure section of the console, click ‘Deployments’.
  2. In the Summary of Deployments page, click on the name of the deployed Web application.
  3. Select the ‘Test’ tab. Here, you’ll find the URL to the deployed Web application. Click the link to launch it in a separate browser window.

oracle UCM 11G – show up blank page?


just clear your browser cache

if not work

work with https

and clear cache




1-  restart of the entire server (not just UCM 11G) seemed to solve the problem.

2- start DB

3- start nodemanager

4- start weblogic

then login with https  and rebuild the index

How to implement SSL in UCM?

Steps needed to setup the Content Server to use SSL are as follows….

1. Open the file <UCM>/config/config.cfg

2. Change the value for HttpServerAddress=http:// … to https://.

3. Add the config entry UseSSL=true

4. Restart the Content Server

5. Start the Admin Applet Weblayout Editor

6. Update the Portal Page

7. If you are using the Folders component make the above config changes to these two files. < UCM>/data/components/folders/config.cfg < UCM>/data/components/folders/install.cfg 8. Restart the content server after all changes have been made.

how to get all schemas at oracle with owners and change them?

SQL> SELECT comp_id, comp_name, version, status, mrc_name, owner FROM schema_version_registry;
COMP_ID    COMP_NAME                      VERSION    STATUS      MRC_NAME   OWNER

———- —————————— ———- ———– ———- —————

BAM        BAM Services          VALID       DEV        DEV_ORABAM MDS        Metadata Services     VALID       SYSMAN     SYSMAN_MDS ORASDPM    SDP Messaging         VALID       DEV        DEV_ORASDPM SOAINFRA   SOA Infrastructure Services VALID       DEV        DEV_SOAINFRA

1. Log in as SYSTEM to the database.
2. Run the following command:

UPDATE system.schema_version_registry$ SET    mrc_name = ‘DEV’, owner = ‘DEV_MDS’ WHERE  mrc_name = ‘SYSMAN’ AND owner = ‘SYSMAN_MDS’;

3. Rerun the “psa”.

how to install jrockit 64 bit,weblogic server at linux?

Download the WebLogic Server installation files from OTN or E-Delivery.

Make sure the JAVA_HOME refers to the proper Java installation:

$ JAVA_HOME=/oracle/jrockit-jdk1.6.0_24 export JAVA_HOME
$ PATH=$JAVA_HOME/bin:$PATH; export PATH

Check that the proper Java version will be used:

$ java -version
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1432-linux-x86_64, compiled mode)

If you are installing WebLogic Server on a 64-bit platform using a .jar installation program use the downloaded wlsversionnumber_generic.jar . Start the installation using the following command. Include the -d64 flag in the installation command when using a 32/64-bit hybrid JDK.

$ java -d64 -jar wls1035_generic.jar

How to install Active Directory Tools Under Windows 7 ?

post source
First of all you need to download the software from Microsoft. In the Microsoft Download Centre these are called “Remote Server Administration Tools for Windows 7” a direct link to the download page is given below;

If you scroll down to the “Files in This Download” section of the page you’ll see two files. Depending on whether or not you’re running 32-bit or 64-bit Windows 7 you need to pick the correct file. If you’re unsure of which version you’re running then go to the start button, right-click “Computer” and then select “Properties”. You’ll see something like this;

System Information (64-bit/32-bit)

Look at the “System type:” value and you’ll see what version of Windows you’re running.

If you’re running 32-bit then you need to download the file which starts “x86…” (currently this is “x86fre_GRMRSAT_MSU.msu” but it might change). For 64-bit users you need to download the file which begins “amd64…” (currently this is “amd64fre_GRMRSATX_MSU.msu”) – this is true even if you’re running a non-AMD 64-bit processor. The reason for this I’ll leave Microsoft to explain …

Once you’ve got the file install it (it’s a standard KB update file).

After it’s been successfully installed go to the Start Menu > Control Panel and select “Programs”;

“Turn Windows Features on or off” under “Programs and Features”

The “Windows Features” dialog box will be displayed, scroll down to “Role Administration Tools” (under “Remote Server Administration Tools”) and select the the following items;

“Windows Features” dialog

Click “OK” to make the changes.

In order to make finding these under the Start Menu a little easier right-click the Start Button and select “Properties”;

Taskbar and Start Menu Properties

Select “Customize …” and then scroll down the list until you see “System administrative tools” and choose where you want the tools to display;

Customize Start Menu

Under the Start Menu you will now see an “Administrative Tools” option, under this you’ll see the new AD Tools;

Active Directory Start Menu Items

NOTE: Sometimes a reboot is required to pick up these changes!