Start managed Server command

Running in Server 2
./startManagedWebLogic.sh "ManagedServer_2" "http://10.3.243.11:7001"

Running in Server 1
./startManagedWebLogic.sh "ManagedServer_1" "http://10.3.243.11:7001"

Creating and Starting a Managed Server on a Remote Machine

I have tried this guide and create successfully Remote Managed Server!

3 Creating and Starting a Managed Server on a Remote Machine

In some domains, you may want to run a managed server on a machine that is remote from the administration server for the domain. You can do this by performing the following steps:

1.

Create a managed server template by using the pack command. A managed server template, by default, contains only those files that are necessary for creating a managed server on a remote machine.

For more information, see Section 3.1, "Creating a Managed Server Template."
2.

Create a managed server domain directory by copying and unpacking the managed server template on a remote machine.

For more information, see Section 3.2, "Creating a Managed Server on a Remote Machine."
3.

Start the managed server on the remote machine.

For more information, see Section 3.3, "Starting Managed Servers on a Remote Machine."

3.1 Creating a Managed Server Template

You create a managed server template by executing the pack command on an existing domain that includes the definition of one or more managed servers and contains managed server definitions in the config.xml file.

1.

From the command line on the local machine (that is, the machine that contains the administration server and the definition of managed servers), navigate to the MW_HOME\wlserver_10.3\common\bin directory.
2.

Run the following command:

pack -managed=true -domain=domain -template=template.jar -template_name="template_name"

In this command:
*

domain is the full or relative path of the domain from which the template is to be created.
*

template.jar is the full or relative path of the template, and the filename of the template to be created.
*

template_name is a descriptive name for the template, enclosed in quotes.

For example, the following command creates a managed server template named mydomain_managed.jar from a domain named mydomain.

pack -managed=true -domain=C:\oracle\user_projects\domains\mydomain -template=C:\oracle\user_templates\mydomain_managed.jar -template_name="My Managed Server Domain"

3.2 Creating a Managed Server on a Remote Machine

1.

Install WebLogic Server on the machines on which you want to host managed servers for the domain.

Note:
All WebLogic Server instances within a domain must run the same version of the WebLogic Server software. For more information about installing WebLogic Server, see the Oracle WebLogic Server Installation Guide.
2.

Establish a session with the remote machine. You may use any valid method, such as telnet, to do so.

The IP address and port number of the remote machine must match the definition of the managed servers specified in the managed server template.
3.

Copy the managed server template to the remote machine.
4.

On the remote machine, navigate to the WLS_HOME\common\bin directory.
5.

Run the following command:

unpack -domain=domain -template=template.jar

In this command:
*

domain is the full or relative path of the domain to be created.
*

template.jar is the full or relative path of the managed server template that you copied to the machine in step 3.

For example, the following command creates a domain named myManagedDomain.

unpack -domain=C:\oracle\user_projects\domains\myManagedDomain -template=C:\oracle\user_templates\mydomain_managed.jar

3.3 Starting Managed Servers on a Remote Machine

When you create a domain directory for managed servers by using the unpack command, it contains a customized start script for each managed server targeted to the current remote machine.

For example, if you create a domain that contains two managed servers, my_managed_server1 and my_managed_server2, and you target the servers to machine m1, when you create the managed server domain directory on machine m1, four custom start scripts are created: startmy_managed_server1.cmd, startmy_managed_server1.sh, startmy_managed_server2.cmd, and startmy_managed_server2.sh. You can use these scripts to start the corresponding managed servers. Alternatively, you can use the startManagedWebLogic script with the required parameters.

1.

Start the administration server for the domain as described in Starting and Stopping Servers.
2.

On the remote machine, navigate to the directory for the domain that you created in How Do I Create a Managed Server on a Remote Machine.
3.

Start the managed server on the remote machine.
*

On a Windows system, run one of the following commands at the DOS prompt:

startmy_managed_server

startManagedWebLogic my_managed_server admin-url
*

On a UNIX system, run one of the following commands:

./startmy_managed_server.sh

./startManagedWebLogic.sh my_managed_server admin-url

In these commands, my_managed_server is the name of the managed server to be started and admin-url is the listen address (host name or IP address) and port number of the machine hosting the administration server. For your convenience, the startManagedWebLogic_Readme.txt file provides a list of all the managed servers and the admin-url for the domain.

Note:
You can also start managed servers by using the node manager. For more information, see Node Manager Administrator's Guide for Oracle WebLogic Server.

Source: Oracle Documents

Command used to Remote from my OpenSuse laptop 11.1 to Ubuntu 9.04 desktop

ssh -XC haibang@192.168.1.37 gnome-panel

Remote controlling ubuntu with x2x

Remote controlling ubuntu with x2x

Using x2x with SSH

This method is based on the method described in here, and is simpler and much more secure than other methods commonly described.

In this example we will use the names 'workstation' for the computer you want to use your mouse/keyboard on, and 'laptop' for the one you want to control. We will also assume that the workstation is to the left of the laptop.

First, on the laptop (the machine you want to control), install x2x and the ssh server:

sudo aptitude install x2x openssh-server

Then, start an X11 session (log in) locally on the laptop. Finally, on the workstation (where you want to use the mouse and keyboard from), login through ssh to the same user account on laptop and launch x2x:

ssh -XC user@laptop x2x -east -to :0.0

Type in the password for the user on the laptop when it asks. And that's all: you should be able to move the mouse smoothly from the workstation monitor to the laptop screen and back.

Next, you can create a launcher on the desktop to make it easy to start it up: right click on the desktop, select 'Create Launcher...', and copy the ssh line from above into the 'Command' section.

Troubleshooting

If you get an error when running x2x:

x2x - error: can not open display

Make sure you included the '-X' bit on the ssh command. Next, you need to make sure 'X Forwarding' is enabled. This is enabled in ubuntu by default, but if for some reason it's not, you need to edit /etc/ssh/sshd_config and uncomment the line that says:

X11Forwarding yes

One additional caveat: If you are using a login manager such as gdm, you must enable remote TCP connections to the X server. In Ubuntu 8.04.1 run the command

sudo /usr/sbin/gdmsetup.

Select the Security tab and uncheck the "Deny TCP connections to the Xserver" checkbox.

Or, just edit /etc/gdm/gdm.conf-custom and add DisallowTCP=false under [security] section.

[security]

DisallowTCP=false

Using x2x

You can change '-east' to '-west', '-north' or '-south' to change which side of the workstation opens up to the laptop, depending on your setup.

For more x2x options, consult the man page of x2x(1):

man x2x

Install Liferay 5.2.3 successfully on WebLogic 10.3.1

Running with no errors!

Start X Server on Sun Solaris 10

#/usr/openwin/bin/kdmconfig
# /usr/openwin/sbin/kdmconfig
# /usr/openwin/sbin/kdmconfig

How to Configure Oracle Web Cache to Listen on Port < 1024

10.0 How to Configure Oracle Web Cache to Listen on Port <>

On most Unix platforms, a process without root privilege cannot listen on ports <>

1. Through the Web Cache Manager, change process identity to the desired running process identity, such as nobody/nobody; change Oracle Web Cache listening port to the desired port, such as 80;
2. log in as root;
3. change the owner of the executable 'webcached' to root;

$ chown root /opt/oracle/webcache/bin/webcached

4. change the group of the executable 'webcached' to the group id of the desired running process identity, such as nobody:

$ chgrp /opt/oracle/webcache/bin/webcached

5. add set-user-id permission to the executable 'webcached';

$ chmod u+s /opt/oracle/webcache/bin/webcached

6. exit from root;
7. start Oracle Web Cache through webcachectl. Oracle Web Cache should be listening on the desired port with the desired process identity (nobody/nobody).

$ /opt/oracle/webcache/bin/webcachectl start

Note that NOT running Oracle Web Cache as root will limit the number of connection handles that Oracle Web Cache can use to the operating system's hard-coded file descriptor limit. See Also: Section 5.0.

Kill Firefox

On Solaris 10:

To find firefox pid:

pgrep -l firefox

To Kill it:

pkill firefox

Trick to Install Jiveforum 4.2.2 on Oracle AS 10.1.3.4

After install Jive Forum, set DB connect, set JiveHome, copy license file. I can access to admin page but cant access to /forum page.
Just go to

/$ORACLE_HOME/j2ee/icb_app4/application-deployments/forum/forum

and change the tag:

jsp-cache-tlds="standard" to jsp-cache-tlds="on"