• No results found

DEPLOYING WEBTOP 6.8 ON JBOSS 6.X APPLICATION SERVER

N/A
N/A
Protected

Academic year: 2021

Share "DEPLOYING WEBTOP 6.8 ON JBOSS 6.X APPLICATION SERVER"

Copied!
11
0
0

Loading.... (view fulltext now)

Full text

(1)

DEPLOYING WEBTOP 6.8 ON JBOSS

6.X APPLICATION SERVER

ABSTRACT

This white paper explains how to deploy Webtop 6.8 on JBoss 6.x application server. November 2014

(2)

2

To learn more about how EMC products, services, and solutions can help solve your business and IT challenges, contact your local representative or authorized reseller, visit www.emc.com, or explore and compare products in the EMC Store

Copyright © 2014 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided “as is.” EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

VMware and <insert other VMware marks in alphabetical order; remove sentence if no VMware marks needed. Remove highlight and brackets> are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other

trademarks used herein are the property of their respective owners. Part Number H13715

(3)

TABLE OF CONTENTS

EXECUTIVE SUMMARY ... 4

 

AUDIENCE ... 4 

STEPS TO START/STOP JBOSS 6.X ... 4

 

STEPS TO DEPLOY WEBTOP THROUGH JBOSS MANAGEMENT CONSOLE .... 4

 

STEPS TO DEPLOY WEBTOP WITHOUT USING MANAGEMENT CONSOLE .. 10

 

STEPS FOR ACCESSING JBOSS MANAGEMENT CONSOLE ... 10

 

(4)

4

EXECUTIVE SUMMARY

This white paper helps customers to deploy Webtop 6.8 on JBoss 6.x application server.

AUDIENCE

This white paper is intended for System Administrators who deploy Webtop 6.8 on JBoss 6.x application server.

STEPS TO START/STOP JBOSS 6.X

Let us say JBoss is deployed in c:\ JBoss-eap-6.3 for windows and /home/JBoss-eap-6.3 for Linux. We will refer to this path as <JBoss-Home>

Windows:

JBoss can be started by executing the following command at the path <JBoss-Home>\bin: standalone.bat JBoss can be stopped by hitting Ctrl+c at the command prompt where you have started the server Linux:

JBoss can be started by executing the following command at the path <JBoss-Home>/bin: ./standalone.sh -bmanagement 0.0.0.0 JBoss can be stopped by hitting Ctrl+c at the terminal where you have started the server

STEPS TO DEPLOY WEBTOP THROUGH JBOSS MANAGEMENT CONSOLE

1) Copy the Webtop.war to a location say c:\Webtop68 for windows /home/Webtop68 for Linux. We will refer to this location

as <WEB-APP-Root>

2) Extract the war contents using the using the following command executed at the path <WEB-APP-Root>: jar –xvf Webtop.war

Note: Use command prompt in windows and terminal in Linux for command execution 3) Move Webtop.war to a different location

4) Update the dfc.properties with the repository details under APP-Root>\WEB-INF\classes for windows and <WEB-APP-Root>/WEB-INF/classes for Linux

5) Stop the JBoss server

6) Generate the encrypted passwords for the users 'dmc_wdk_presets_owner' and 'dmc_wdk_preferences_owner'  and update the passwords in app.xml under <WEB‐APP‐Root>\wdk for windows and <WEB‐APP‐Root>/wdk for  Linux    7) Do the following JBoss EAP 6.x specific changes in Webtop :       a.  If present, delete the dfc.keystore and wdk.keystore files under <JBoss‐Home> \bin for windows and  <JBoss‐Home> /bin for Linux and move the keystore files from < WEB‐APP‐Root >\WEB‐INF\classes for  windows and < WEB‐APP‐Root >/WEB‐INF/classes for Linux to the bin folder. The keystore files would be  generated by step 6    b. Also delete the documentum folder under < WEB‐APP‐Root >\WEB‐INF\classes for windows and < WEB‐ APP‐Root >/WEB‐INF/classes for Linux generated by step 6   

(5)

c. Copy the contents of the classes folder under < WEB‐APP‐Root >\WEB‐INF\classes for windows and <  WEB‐APP‐Root >/WEB‐INF/ classes for Linux  into a temporary location say <temp‐loc> and create a jar  file 'web‐inf‐classes.jar'  using the following command executed at the path <temp‐loc> :     jar ‐cvf web‐inf‐classes.jar *    d. Copy the web‐inf‐classes.jar to < WEB‐APP‐Root >\WEB‐INF\classes\lib in windows and < WEB‐APP‐Root  >/WEB‐INF/classes/lib in Linux    e. Delete the classes folder under < WEB‐APP‐Root >\WEB‐INF in windows and    < WEB‐APP‐Root >/WEB‐ INF in Linux    f. Disable tag pooling in JBoss by adding the following entry in subsystem tag in standalone.xml under  <JBoss‐Home>\standalone\configuration in windows and <JBoss‐Home>/standalone/configuration in  Linux :      <subsystem xmlns="urn:JBoss:domain:web:2.1" default‐virtual‐server="default‐host"  native="false">  <connector name="http" protocol="HTTP/1.1" scheme="http" socket‐binding="http"/>   <virtual‐server name="default‐host" enable‐welcome‐root="true">  <alias name="localhost"/>  <alias name="example.com"/>  </virtual‐server>  <configuration>  <jsp‐configuration tag‐pooling="false"/>  </configuration>  </subsystem>    g. Also configure the binding address by replacing 127.0.0.1 with the appserver host IP address in  <wsdl‐host> tag and <interfaces> tag in standalone.xml    h. Repackage the Webtop war file using the following command executed at < WEB‐APP‐Root >:  jar –cvf Webtop.war *   Copy the repackaged war to a location say c:\Webtop68war for windows and /home/Webtop68war  for Linux    8) Start the JBoss server   

(6)

6

9) Login to the JBoss EAP 6.x management console by accessing the URL http://<AppServer‐host>:9990/console 

and entering the administrative user credentials 

10)  Click on Runtime tab and click on Manage Deployments node   

(7)

11) Click on Add button and select the Webtop.war under c:\Webtop68war for windows and /home/Webtop68war  for Linux  and click Next 

 

(8)

8

12) In the Verify Deployment Names step, click Save                 

(9)

    13) Select the deployment under Available Deployments and click the button Enable/Disable and click Confirm to  enable the deployment     

(10)

10

 

STEPS TO DEPLOY WEBTOP WITHOUT USING MANAGEMENT CONSOLE

Webtop can also be deployed without using the management console by following the below mentioned steps:  1) Repeat Steps 1‐7 from the previous section    2) Copy the Webtop.war file to the location <JBoss‐Home>\standalone\deployments in windows and <JBoss‐ Home>/standalone/deployments in Linux    3) Start the JBoss server   4) Check if deployment is successful in server.log under <JBoss‐Home>\standalone\log in windows and <JBoss‐ Home>/standalone/log in Linux  5) Access Webtop URL : http://<AppServer‐host>:8080/Webtop   

STEPS FOR ACCESSING JBOSS MANAGEMENT CONSOLE

Initial administrative user has to be created to access the management console    Administrative user can be created in windows by executing the following command at the path <JBoss‐Home>\bin:  add‐user.bat    User can be created in Linux by executing the following command at the path <JBoss‐Home>/bin:  ./add‐user.sh    Then follow the following steps to create the user:    1) Choose to add a Management user:    Hit ENTER to select the default option a to add a management user.     This user is added to the Management Realm and is authorized to perform management operations using  the web‐based Management Console    The other choice b adds a user to the Application Realm, and provides no particular permissions. That realm  is provided for use with applications.    2) Enter the desired username and password:  When prompted, enter the username and password. You will be prompted to confirm the password.   

(11)

3) Enter group information:  Add the group or groups the user belongs to. If the user belongs to multiple groups, enter a comma  separated list. Leave it blank if there are no groups for the user.    4)  Review the information and confirm:    You are prompted to confirm the information. If you are satisfied, type yes.    5) Choose whether the user represents a remote JBoss EAP 6 server instance.    For the purposes of this task, answer no to this question   

Then access the management console by hitting the URL: http://<AppServer‐host>:9990/console and entering the  administrative user credentials   

TROUBLESHOOTING TIPS:

  1) In Linux, if you are unable to access Webtop or management console even though server is started properly,  firewall may have blocked the ports 8080 and 9990.    The ports can be unblocked by executing the following command:  iptables ‐I INPUT ‐p tcp –dport <port‐no>  ‐‐syn ‐j ACCEPT    2) If we do not use ‐bmanagement 0.0.0.0 option when starting the server, management console won’t be  accessible even if server is started because it gets bound to loopback address 127.0.0.1  Hence, we should either use ‐bmanagement 0.0.0.0 option when starting the server or configure the binding  address in standalone.xml 

CONCLUSION

References

Related documents

The results shows that Polish respondents underestimate the relational factors like: active entrepreneurs in initiating cooperation, responsiveness, openness, trust, and

Positions on Local Section Boards – Many local sections with young professional groups try to involve young professionals on their boards.. Local sections recruit young people

The present paper contributes to the ongoing debate about how international trade can affect the demand for skills in industrial countries by estimating the impact of

These viruses modify their code on each infection (each infected file contains a different These viruses modify their code on each infection (each infected file contains a different

Insulin-like growth factor receptor 1 (IGF1R) gene copy number is associated with survival in operable non-small cell lung cancer: a comparison between IGF1R

CODING AND QUANTIZATION LOSSES FOR THE COHERENT WHITE GAUSSIAN

pathogen enters the blood stream, the Second Line of Defense, macrophage white blood cells, attack the invaders. If they cannot defeat the

immigration, migration, refugees, asylum, Syria, Honduras, Cuba, empathy, storytelling, narrative, Cuban Adjustment Act, Temporary Protected Status, deferred action, parole, policy,