aspose file tools*
The moose likes Websphere and the fly likes Deploying from WSSD Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Deploying from WSSD" Watch "Deploying from WSSD" New topic
Author

Deploying from WSSD

Steve McCain
Ranch Hand

Joined: Sep 03, 2001
Posts: 45
I have WSSD 5.1 on my PC (W2000 Prof). I have WAS 5.0 running on a Solaris box. I've installed the Remote Agent Controller that was supplied with WSSD
on the Solaris box, it starts OK.
I thought I would test out the ability to deploy apps direct from WSSD to WAS so in WSSD I created a Server project & have tried to create a new server & server config. I select the appropriate server type in the wizard. On the next screen I give it the IP address of the Solaris box. When I click 'next' WSSD tries to connect but I always get "Connection Failed on host xxx.xx.xx.xx. Make sure that the Agent Controller is installed etc etc".
I have changed the RAC serviceconfig.xml to include <Allow host="ALL">. The port is the default 10002. What am I missing?
On a wider front, can anyone point me to some helful documentation of deploying applications via RAC? The Websphere Help System (Infocenter) doesn't help me at all nor does the help avaliable in WSSD.
IBM Tech Support don't seem able to help either - I was recommended just to deploy apps via AAT & the Admin console.
Anyone got any experience of RAC - is it worth pursuing or am I wasting my time???
Steve McCain
Ranch Hand

Joined: Sep 03, 2001
Posts: 45
Sorry, I meant to say that I have set Allow Hosts= "ALL" in serviceconfig.xml
Mahesh Chalil
Ranch Hand

Joined: Jan 24, 2002
Posts: 147
As an IBM Websphere experienced guy, my polite request will be to take your ear file and deploy it using Websphere Admin Console. If you think about it, dont you think thats the easiest way?;-) Bcos WAS5.0 support both remote and local ear file deployment using Admin console.
If you still want to fight with that, try following:
Creating a server for remote testing (WebSphere Application Server)
Prerequisites:
If you want to test your projects remotely on WebSphere Application Server, you must install the following software on the remote server:
IBM WebSphere Application Server
IBM Agent Controller
(Optional) FTP server
When creating a server, you can specify a remote server as the server type if you wish to test on a remote installation of WebSphere Application Server. In this case, you must specify additional information about how to transfer files to the remote test server.
On the first page of either the Create a New Server wizard (File > New > Other > Server > Server) or the Create a New Server and Server Configuration wizard (File > New > Other > Server > Server and Server Configuration), select WebSphere Remote Server as the server type. Click Next.
In the Host address field, type the fully qualified DNS name or the IP address of the remote machine that WebSphere Application Server is running on. The field is pre-filled with the default address for the local host (127.0.0.1). For more information about any of the fields on this and other wizards, select the field and then press F1.
Click Next. The WebSphere Remote Server Settings page of the wizard allows you to provide additional information required for using WebSphere Application Server remotely. Note that all the paths on this page are as seen from the remote machine.
In the WebSphere installation directory field, type the path where you installed WebSphere Application Server on the remote machine. This path is the same as the WAS_ROOT path mappings as defined by the WebSphere server configuration. For example, if you have installed WebSphere Application Server in C:\WebSphere\AppServer, then use this as the WebSphere installation path.
If you want to use the default WebSphere deployment directory, select the Use default WebSphere deployment directory check box.
If you select the Use default WebSphere deployment directory check box when creating a remote server and then you publish to this server, the default WebSphere Application Server server-cfg.xml file is replaced with the published version. For more information about the replacement of this file, refer to Replacement of default WebSphere Application Server files.
If you do not want to use the default WebSphere deployment directory, clear the Use default WebSphere deployment directory check box and in the WebSphere deployment directory field, type the path of the directory where the Web application and server configurations will be published. This directory is any existing directory that can be seen from the remote server machine. For example, if the directory E:/testdir resides on the remote machine, then type E:/testdir in this field.
Important: If you select the Use default WebSphere deployment directory check box when creating a remote server and you also select the Generate plug-in configuration file check box when editing a remote server and then publish using this server, the default WebSphere Application Server server-cfg.xml file and plugin-cfg.xml files are replaced with the published version. For more information about the replacement of this file, refer to Replacement of default WebSphere Application Server files.
However, if you are following WebSphere naming conventions and install WebSphere Application Server in the C:\WebSphere\AppServer directory, then the WebSphere deployment directory is C:\WebSphere\AppServer.
When publishing to the remote server, the server configuration and the Web application will be published to a directory under the remote deployment directory called config and installedApps respectively.

(Optional) In the DB2 driver location field, type the DB2 location where the DB2 classes reside in the remote machine. You can set a default value in the WebSphere preferences page (Window > Preferences > Server > WebSphere).
Click Next again to display the Create or Select a Remote File Transfer page of the wizard. A remote file transfer contains information for transferring Web applications and server configurations to the remote server during publishing.
Select one of the following radio buttons:
Create a new remote file transfer defines a new set of parameters and environment settings needed to transfer files remotely.
Use an existing remote file transfer lists the already defined remote file transfer that you can use for transferring files remotely.
If Create a new remote file transfer radio button is selected:
From the list, select one of the following:
Copy file transfer mechanism to copy resources directly from one machine to another in the file system.
FTP file transfer mechanism to copy resources from one machine to another using File Transfer Protocol (FTP).
Click Next to display the fourth page of the wizard.
If Use an existing remote file transfer radio button is selected, the Next button is not enabled. Select the remote file transfer that you want to use to transfer files remotely. Omit the next step.
If Copy file transfer mechanism is selected, the next page of the wizard is the Create a New Server and Server Configuration page.
In the Project folder field, type the name of the project folder where the remote file transfer will reside.
In the Remote file transfer name field, type the name of the remote file transfer. For more information about any of the fields on this and other wizards, select the field and then press F1.
In the Remote target directory field, type the remote target directory where you want your applications and server configuration published. This remote target directory is the one seen by the local machine. If WebSphere Application Server is installed on a different machine, then the remote target directory is the network drive that maps to the WebSphere deployment directory. If WebSphere Application Server is installed on the same machine as the workbench, then the remote target directory should be the same as the contents in the WebSphere deployment directory field. For example, C:/WebSphere/AppServer.
The Next button is enabled only if you are creating a new server and configuration together. Click Next if you want to change the HTTP port number.
If FTP file transfer mechanism is selected, the next page of the wizard opens.
In the Project folder field, type the name of the project folder where the remote file transfer will reside.
In the Remote file transfer name field, type the name of the remote file transfer.
In the Remote target directory field, type the remote target directory where you want your application and server configuration published. This remote target directory points to the WebSphere deployment directory that is seen from the workbench using the FTP client program. For example, if the WebSphere deployment directory is C:/WebSphere/AppServer and your FTP server route directory is C:/, then your remote target directory is /WebSphere/AppServer.
To determine whether a beginning slash is required, log on to the FTP server using a FTP client program, and then type the pwd command. If the results containing the default log on directory begins with a slash, then a slash is required prior to typing the remote target directory in the Remote target directory field.
In the FTP URL field, type the URL that is used to access the FTP server.
In the User login field and the User password field, type the FTP user ID and password that will be used to access the FTP server.
In the Connection timeout field, type the time (in milliseconds) that the workbench will attempt to contact the FTP server before timing out.
Select the Use PASV Mode (Passive Mode) to go through the firewall check box, if you want to pass through a firewall provided that one is installed between your FTP server and the workbench.
Select the Use Firewall check box, if you want to use the firewall options.
To change the firewall options, select the Use Firewall check box, and then click Firewall Settings to specify and settings.
The Next button is enabled only if you are creating a new server and server configuration together. Click Next if you want to change the HTTP port number.
Click Finish to create a remote file transfer and a remote server. These servers will reside locally on your machine. The servers appear in the Server Configuration view. The remote file transfers appear in the Navigator view.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Deploying from WSSD
 
Similar Threads
Where from I get Remote Agent Controller?
Problem in using IBM Agnet Controller
Problem in Agent controller in WSAD
WSAD and WebSphere application server
Remote Agent Controller