Learnt that plugin setup for WAS is different from the setting up in BEA weblogic environment.
WAS plugin require an installation while we just need to put in the plugin for BEA weblogic. Here's the steps to get WAS running.
Installing the Plugin in the web server.
Download the installation file from IBM. i.e. "Tiv_Middl_Inst_750_1of3_Linux_x86-64.tar" since i'm using linux for my web server.
Transfer the tar file into the web server and unpack.
Was only able to install using the supplied GUI so be prepared to export display.
# cd linux64/WS-WAS_ND_7.0_Supplemental
# gunzip C1G36ML.tar.gz
# tar xfp C1G36ML.tar
# cd plugin
# export BROWSER=/usr/bin/mozilla
# export DISPLAY=10.10.10.16:0.0
# ./launchpad.sh
| need to have your xwin or xmanager ready. |
My template cfg.xml file is now at "/opt/IBM/WebSphere/Plugins/config/myapp/plugin-cfg.xml"
Copy the configuring script to the WAS server.
There is a customised configuration script that you need to run at
the WAS server to generate the real cfg.xml file. It is usually in the
plugin bin, i.e.
"/opt/IBM/WebSphere/Plugins/bin/configuremyappserver.sh"
copied this to the root directory of WAS, i.e. /opt/was/IBM/WebSphere/AppServer/bin and run it.
Next, generating the plugin xml file in WAS server.
root@myappserver:/opt/was/IBM/WebSphere/AppServer/bin> ./configuremyappserver.sh
Realm/Cell Name: <default>
Username: wasuser
Password:
WASX7209I: Connected to process "dmgr" on node myappserverCellManager01 using SOAP connector; The type of process is: DeploymentManager
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[myapp, APACHE, /usr/local/apache2222, /usr/local/apache2222/conf/httpd.conf, 80, MAP_ALL, /opt/IBM/WebSphere/Plugins, unmanaged, mywebserver-node, mywebserver, linux]"
Input parameters:
Web server name - myappserver
Web server type - APACHE
Web server install location - /usr/local/apache2222
Web server config location - /usr/local/apache2222/conf/httpd.conf
Web server port - 80
Map Applications - MAP_ALL
Plugin install location - /opt/IBM/WebSphere/Plugins
Web server node type - unmanaged
Web server node name - mywebserver-node
Web server host name - mywebserver
Web server operating system - linux
Creating the unmanaged node mywebserver-node .
Unmanged node mywebserver-node is created.
Creating the web server definition for myapp.
Web server definition for myapp is created.
Start computing the plugin properties ID.
Plugin properties ID is computed.
Start updating the plugin install location.
Plugin install location is updated.
Start updating the plugin log file location.
Plugin log file location is updated.
Start updating the RemoteConfigFilename location.
Plugin remote config file location is updated.
Start updating the RemoteKeyRingFileName location.
Plugin remote keyring file location is updated.
Start saving the configuration.
Configuration save is complete.
Computed the list of installed applications.
Processing the application myapp.
Get the current target mapping for the application myapp.
Computed the current target mapping for the application myapp.
Start updating the target mappings for the application myapp.
Target mapping is updated for the application myapp.
Start saving the configuration.
Configuration save is complete.
Transfer the plugin-cfg.xml file to the web server.
scp /opt/was/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/myappserverCell01/nodes/mywebserver-node/servers/myapp/plugin-cfg.xml user@mywebserver:/tmp/
| The
generated file is generally in
"profiles_install_root/config/cells/cell_name/nodes/node_name/servers/web_server_name"
directory |
| The place to put the plugin-cfg.xml file is generally in "plugins_install_root/config/web_server_name" directory |
Start up Apache and test.
you should be good to go.
No comments:
Post a Comment