Download and install WebLogic 10.3 on the servers of the cluster and don't forget the install the nodemanager. You don't have to install Workshop for WebLogic
WebLogic will use a database as domain repository. In my case I will use MySQL as database. Off course you can use an Oracle database too. In the bea_home\wlserver_10.3\server\lib folder there are some scripts to create the weblogic repository. For Oracle is this the "rdbms_security_store_oracle.sql" file. Too bad there isn't a script for the MySQL database so I changed one of the scripts so it matches MySQL ddl.
Add two or more managed servers to this domain.
Create a new cluster and add the two managed servers to this cluster.
Add the node managers to this domain.
Add the AdminServer and Managed Server 1 to the first machine and Managed Server 2 to the second.
The last step is to give this domain a name and storing this domain in the user_projects folder
Start the Admin Server and after this you can start the Admin Server Console.
Go the control tab of the Servers where we can start the first managed server. Make Sure the node manager is running on this server.
To start the second managed server we have to do a little more. We need to pack the domain configuration on the first machine and unpack this on the second machine. After this we can start this second managed server.
go to this folder D:\Apps\bea\wlserver_10.3\common\bin>
pack -managed=true -domain=D:\Apps\bea\user_projects\domains\mhs_domain -template=d:\apps\mhs_domain_template.jar -template_name="mhs domain"
On the second machine we can unpack this domain
unpack -domain=D:\Apps\bea\user_projects\domains\mhs_domain -template=mhs_domain_template.jar
Now we can go back the console and start the second managed server. ( Be sure that the node manager is started on this machine)
If you want JMS clustering then you need to make a JMS server on all managed nodes.
Create a Connection Factory which has the Cluster as subdeployment. The last step is to create a distributed Queue or Topic.