2.1. MARCO TEÓRICO
2.1.2. VARIABLE DEpENDIENTE
2.1.2.2. Toma de decisiones
2.1.2.3.1. Nivel de confianza de las personas hacia los servicios que
test on a remote installation of WebSphere Application Server. In this case you have to do the following steps:
1. In the Server view of the Server perspective, create the server configuration for the new remote Application Server: New —> Server Instance and Configuration. Fill in and select in the fields like below (Figure 8-18): a. Server Name: Enter a display name for the new server.
b. Folder: Enter a folder name for the server.
c. Select WebSphere Remote Server as server type.
Chapter 8. Deploying the Web application 165 2. Click Next. The next window appears to specify the Host address of the
remote server (Figure 8-19). Type the fully qualified DNS name, or the IP address of the remote server machine where WebSphere Application Server is running.
Figure 8-19 Setting the remote server host address
3. Click Next. In the next window (Figure 8-20), type in the WebSphere installation directory field in the path where you installed WebSphere Application Server on the remote machine. This path is the same like the $WAS_ROOT variable:
a. WebSphere Installation directory is the directory where the Application Server is installed: i.e. /opt/WebSphere/AppServer
b. Use default WebSphere deployment directory check box when you creating a remote server to publish to this server. If do not want to use the WebSphere deployment directory, clear the check box and enter the WebSphere deployment directory field a new path directory name where the Web application and server configuration has to be published to the remote directory in the directories called config and installedApps.
c.
Optional
: In the DB2 driver location field enter the DB2 location where the DB2 classes reside in the remote directory.d. Choose in the check box below the platform of the remote machine. It depends on which kind of platform your remote machine is running (for Linux choose Other).
Figure 8-20 Remote server instance settings
4. Click Next. The following page allows you to create a remote file transfer instance (Figure 8-21).It contains information for transferring Web
applications and server configurations to the remote server during publishing. Select one of the following radio buttons:
a. Create a new remote file transfer instance, it defines a new set of parameters and environment settings needed to transfer files remotely. i. Copy file transfer mechanism to copy resources directly from one to
another in the file system.
ii. FTP file transfer mechanism copy resources from one machine to another using File Transfer Protocol (FTP)
b. Use an existing remote file transfer instance lists the already defined remote file transfer instances that you use for transferring files remotely.
Chapter 8. Deploying the Web application 167
Figure 8-21 Remote file transfer option
c. If Copy file transfer mechanism is selected the next window appears with the following fields (Figure 8-22):
i. Project Folder: Type the name of the project where the remote file transfer will be reside.
ii. Remote file transfer name: Given from the wizard as remote file transfer name (possible to change).
iii. Remote target directory: Type the remote target directory where you want to your applications and server configurations published. This remote target directory is the one seen by the local machine. If WebSphere Application Server 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 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: i.e. /opt/WebSphere/AppServer
Figure 8-22 Remote copy options
iv. Click ext if you want to change the HTTP port number in the next window of the wizard.
v. Click Finish to create a remote server file instance and a remote server instance. The server instances appear in the Server view. The remote file transfer instance appears in the Navigator view of
WebSphere Studio Application Developer.
d. If FTP file transfer mechanism is selected, the next window appears with the following fields (Figure 8-23):
i. Project Folder: Type the name of the project folder where the remote server will reside.
ii. Remote file transfer name: Given from the wizard as a remote file transfer name (Possible to change).
iii. Remote file transfer directory: 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 form the Workbench using the FTP client program.
iv. FTP URL: Type the URL that is used to access the FTP server. v. User login: Type the FTP user ID used to access the FTP server. vi. User password: Type the FTP password used to access the FTP
Chapter 8. Deploying the Web application 169 vii. Connection timeout: Type the time (in milliseconds) that the
Workbench will wait attempting to contact the FTP server before timing out.
viii.Use PASV Mode (Passive Mode) in go through the firewall: Select this check box if you want pass through a firewall provided that one is installed between your FTP server and the Workbench.
ix. Use Firewall: Select the check box if you want to use the firewall options. To change the firewall options, click Firewall Settings to specify and settings.
e. Click Next if you want to change the HTTP port number in the next window of the wizard.
f. Click Finish to create a remote server file instance and a remote server instance. The server instances appear in the Server view. The remote file transfer instance appears in the Navigator view of WebSphere Studio Application Developer.