Home

Globus Online

Globus Toolkit

dev.globus

About Globus

About the Toolkit

Documentation

Downloads

Support

GT 4.0 Java WS Core : System Administrator's Guide
Hom e -> Toolk it -> Docs -> 4.0 -> C om m on -> Javawscore

Search

Table of Contents 1. Introduction 2. Building and Installing 2.1. Building from source 2.2. Installing Core-only binary distribution 3. Configuring 3.1. Configuration overview 3.2. Syntax of the interface: 4. Deploying 4.1. Java WS Core container 4.2. Deploying into Tomcat 5. Testing 6. Security Considerations 6.1. Permissions of service configuration files 6.2. Permissions of persistent data 6.3. Invocation of non-public service functions 7. Troubleshooting 7.1. g o u - t p c n a n rfails with an authorization error lbsso-otie 7.2. g o u - t r - o t i e hangs during startup lbssatcnanr 7.3. Programs fail with j v . a g N C a s e F u d r o : j v x s c r t / . errors aaln.olsDfonErr aa/euiy.. 7.4. C n u r n M d f c t o E c p i nin Tomcat 5.0.x ocretoiiainxeto 7.5. j v . e . o k t x e t o : I v l d a g m n o c n o a s g r q e t d a d e s aantSceEcpin nai ruet r ant sin euse drs 7.6. General troubleshooting information 8. Usage statistics collection by the Globus Alliance

1. Introduction
This guide contains advanced configuration information for system administrators working with Java WS Core. It provides references to information on procedures typically performed by system administrators, including installation, configuring, deploying, and testing the installation. Important This information is in addition to the basic Globus Toolkit prerequisite, overview, installation, security configuration instructions in the GT 4.0 System Administrator's Guide. Read through that guide before continuing unless you are installing the Java core-only installer.

2. Building and Installing
Java WS Core is built and installed as part of a default GT 4.0 installation. For basic installation instructions, see the GT 4.0 System Administrator's Guide. No extra installation steps are required for this component. The following are optional instructions for more advanced types of installations. These are for those advanced users who want to build the latest code from CVS or are just interested in the Java WS Core.

2.1. Building from source
1. Obtain the source code for Java WS Core: From CVS. a. To get the latest source from cvs execute: cs- :sre:nnmu@v.lbsog/oegodvCSgou-akgs\ v d pevraoyoscsgou.r:hm/lbe/V/lbspcae ceku wr hcot sf b. Change into the w r directory. sf c wr d sf From Core-only source distribution. a. Untar or unzip the distribution archive. trxf w-oeXXsctrg a vz scr-X-r.a.z b. Change into the unpacked distribution directory. c w-oeXX d scr-X

2. It is equivalent to setting the G O U _ O T A Eenvironment property.1. The configuration information of a service is mainly encapsulated in two a separate configuration files: server-config.d/ 3. Comments Optional Optional Optional .2.1.generate launch scripts for standard Globus tools such as g i . . Untar or unzip the distribution archive.a l s r p s t u . LBSLCTO ntl 3.g rconfiguration and supports configuration profiles.w n o s n y f l e. The configuration item name corresponds to the "name" attribute in a < a a e e >sub element. All these configuration files are dropped into the $ L B S L C T O / t / g r i > directory during the deployment process. Change into the unpacked distribution directory. Table 1.m GT4 WS Authorization Framework documentation for details. Can be FQDN or just hostname.create and configure the container with a global security descriptor Dnbecnanrds=re 2. LBSHSNM This parameter specifies whether to perform DNS lookup on the l g c l o tparameter. On Windows: LBSLCTO stGOU_OAINc\t e LBSLCTO=:g4 On Unix/Linux: stn GOU_OAIN/otg4 eev LBSLCTO sf/t/ or epr GOU_OAIN/otg4 xot LBSLCTO=sf/t/ If G O U _ O A I Nis not set.o f g x l(security deployment descriptor) file.e a l . s dfiles in the $ L B S L C T O / t / l b s w r _ o e goaCniuain sre-ofgwd GOU_OAINecgou_sfcr/ directory.generate Windows and Unix launch scripts Dl. Please see the Security Descriptor page in the euiycni.n t etc.1. trxf w-oeXXbntrg a vz scr-X-i. Set the G O U _ O A I Nenvironment variable to the unpacked distribution directory. e c t u .r x .contains information about the resource management.2. Configuration overview Java WS Core provides per. This parameter specifies the domain name to append to the host name if the host name is not qualified by a domain.2.xml (JNDI configuration file) . By default " a s "is oiaHs fle assumed (DNS lookup is performed). c w-oeXX d scr-X 3.z 2. Run: atal n l Additional arguments can be specified on the a tcommand line to customize the build: n .a. General configuration parameters Name logicalHost disableDNS domainName Value <hostname> <boolean> <domain name> Description This parameter specifies the hostname to use instead of the default local host.wsdd (Web Service Deployment Descriptor) . and the value is put as a "value" attribute within prmtr the same parameter element.3. (Unix/Linux only) DidwOl=as rdpoyii. o t i e .contains information about the web service. Configuring 3. an i s a ldirectory will be created under the current directory. 3. Set the G O U _ O A I Nenvironment variable to the absolute path of the target directory of your installation. Installing Core-only binary distribution 1. jndi-config. A service that support security might also have the s c r t . Global Configuration The global properties are specified in the < l b l o f g r t o >section of * e v r c n i . On Windows: LBSLCTO stGOU_OAINc\t e LBSLCTO=:g4 On Unix/Linux: stn GOU_OAIN/otg4 eev LBSLCTO sf/t/ or epr GOU_OAIN/otg4 xot LBSLCTO=sf/t/ Note: Please make sure to have the JAAS library installed if running with J2SE 1.cit=re . GOU_OAINec<a. Syntax of the interface: 3.

Table 5. wbplctoNm> Optional Optional (since GT 4.1) Table 2. The service srie srie handle will have the form of <hosting environment URL>/foo. threads 2 2 8 8 Table 4.1. In Tomcat. By default it is set to 3 minutes.RPCProvider. ialDS This parameter specifies the server id. By default it is set to 2 * the c n a n r h e dsetting. Axis Standard Parameters Name className handlerClass Value <class> <class> Description This parameter specifies a class that implements the web service methods. In GT 4.one. each container gets its own persistent directory based on the server id. That is. The configuration information for a service is defined by various < a a e e >sub-elements within a < e v c >element. Comments Required Recommended in our environment .0. the maximum amount of time the container will wait to receive a message from the client. By default.xspoiesRCrvdr/ <aaee nm=soe prmtr ae"cp" vle"plcto"> au=Apiain/ <sliesaeshm/oesmlscutrcutrsriewd<wdFl> wdFl>hr/ceacr/ape/one/one_evc.sfsmlscutrCutrevc"> <aaee nm=hnlrls" prmtr ae"adeCas vle"r.3+ it defaults to 1. By default it is set to 4 * the c n a n r h e dsetting. where: the hosting environment URL typically is h t : / h s > < o t / s f s r i e .onePrTp"> au=cmcutrCutrotye/ <aaee nm=poies vle" prmtr ae"rvdr" au= DsryrvdrStemntoTmPoie GtPrvdr etoPoie eTriainiervdr eRPoie SbciervdrGturnMsaervdr/ usrbPoie eCretesgPoie"> <srie /evc> Services are defined in a < e v c >element. The server id is used to uniquely identify each container instance. This parameter specifies what dispatcher to use to send a request to a service method.1) webContext <name> Table 3. For example. otieTra This parameter controls the container timeout. This parameter sets the maximum number of threads for the container. It enables special features such as operation providers or security support.> The use attribute should be set to literal and the style attribute to document for all WSRF/WSN based services.sl/slie <aaee nm=alwdehdCas prmtr ae"loeMtosls" vle"o.id <boolean> <string> This parameter specifies whether to publish the hostname or the ip address. Service Configuration 3.2.0. The configuration item name corresponds to the "name" attribute in a < a a e e > prmtr srie prmtr sub element. In tp/<ot:pr><eCnet/evcsMSrie sf Tomcat.2.one.providers. tp/<ot:pr>wr/evcs foo is the name of the service (< e v c n m = f o . Default container thread pool settings (GT 4. threads 2 1 20 3 3.lbswr.c n a n r o t ". Comments Optional Optional Optional Optional (since GT 4.0.3+ only) Type standalone embedded Min. Standalone/embedded container-specific configuration parameters Name containerThreads containerThreadsMax containerThreadsHighWaterMark containerTimeout Value <int> <int> <int> <int> Description This parameter controls the initial thread pool size for the container. The "name" attribute of the < e v c >element defines the remotely accessible name of the service. Default container thread pool settings Type standalone embedded Min. By default "w r " name is used. the server id will default to "< p i><otiePr> i> < e A p i a i n a e ".PPoie"> au=oggou. ).0.0. threads Max.oneSrie/ au=oggou. and the value is put as a "value" attribute within the same parameter element. This parameter specifies the context name under which the services are published under: h t : / h s > < o t / w b o t x > s r i e / y e v c .axis. this parameter is always set to the web application's name.rvdr.ape. threads Max. It is only used when DNS lookups are enabled (d s b e N is false).globus.lbsai. If not set.publishHostName server.2) Optional (since GT 4. otieTra This parameter controls when the thread pool of the container should start shrinking (if the number of idle threads exceeds this number). srie ae"o" . WSDD An example of a deployment descriptor for a CounterService: <evc nm=Cutrevc"poie=Hnlr srie ae"oneSrie rvdr"ade" ue"iea"sye"ouet> s=ltrl tl=dcmn" <aaee nm=casae prmtr ae"lsNm" vle"r.2. the standalone container server id is "< p . This parameter is required if the provider attribute of the service is set to P o i e . .2. The default dispatcher we provide is called rvdr org. it defaults to 2.

enatr<vle <prmtr /aaee> <aaee> prmtr <aersucCas/ae nm>eorels<nm> <au>r. The wsdl file must contain the wsdl:service entry.ape. or a class with a type mapping.globus. a new service object is created for each session-enabled client who accesses the service. Application scope is recommended wsdlFile <path> Required in our environment Optional. If Session scope is used.lbswr. The namespace is specified in the { . eoreoe Table 7.lbswr. If Request scope is used.oneHm" <eoreaas rsucPrm> <aaee> prmtr <aefcoy/ae nm>atr<nm> <au>r. This parameter only has effect if used with org. This parameter specifies a space separated list of provider names or class names. Java WS Core Parameters Name loadOnStartup Value <boolean> Description If set to true this parameter will cause the web service and the corresponding ResourceHome (if any) to be initialized (with proper security settings if configured) at container startup.axis.2. The Java type can be for any simple Java type.axis.providers.2. e v c R s u c H m .2. e o r e o e m l eoreoe eoreoe r. a new service object is created for each SOAP request that comes in for the service. this QName will be used to discover the SOAP header that contains the key of the resource in the request. This parameter points to a wsdl file for the service.RPCProvider handlerClass.lbswr.agSrn aaln.lbswr. ResourceHomeImpl The ResourceHomeImpl is a generic and reusable R s u c H m implementation.one. Note: Only Request and Application scopes are supported when used with org. Comments Optional allowedMethodsClass <class> Optional providers <list of providers> Optional Please see Custom Deployment for details on Axis Web Services Deployment Descriptor. Usually the class specified in this parameter would be the remote interface class generated for the service.agItgr/au> <prmtr /aaee> <rsucPrm> /eoreaas <rsuc> /eore <srie /evc> Each service in WSDD should have a matching entry in the JNDI configuration file with the same name.2.o}oneKy/au> vle{tp/cutrcmCutre<vle <prmtr /aaee> <aaee> prmtr <aersucKyye/ae nm>eoreeTp<nm> <au>aaln. By default all methods are allowed. hm" atr r. only a single instance of the service object is created and used for all SOAP requests that come in for the service.sfsmlscutrCutroe> ye"r. Defaults to jv. This parameter specifies the type of the resource key as a Java class.niBaFcoy/au> vleoggou.globus. " " * indicates that all methods of the service class can be invoked via SOAP.nee<vle vlejv. resource caching.globus. The key XML element is deserialized into this Java type. A relative file location is recommended.niBaFcoy 3.providers. JNDI An example of a JNDI configuration bit for a CounterService: <evc nm=Cutrevc" srie ae"oneSrie> <eore rsuc nm=hm" ae"oe tp=oggou.scope <value> Scope value can be one of: Request (the default). It supports persistent resources. Axis generated bean. Please see the JNDI section for details. If Application scope is used.2. e n a t r value. It is useful for easily restricting the SOAP-accessible methods of the service. This parameter only has effect if used with org. allowedMethods <list of methods> Table 6. etc. r.essetone<vle vleoggou. The file location can be relative or absolute.sfsmlscutrPritnCutr/au> <prmtr /aaee> <aaee> prmtr <aersucKyae/ae nm>eoreeNm<nm> <au>ht:/one.mlRsucHmIp and o g g o u .axis.sfjd. Application. etc.2.ape. Each service entry in JNDI should have a resource defined called " o e . Comments Required resourceKeyType <class> Optional. resource sweeper. s f i p . Currently we have two main base R s u c H m implementations: o g g o u . Under each service entry in JNDI different resource objects or entries might be defined. or Session.providers. That hm" resource is the ResourceHome implementation for the service (as specified by the t p attribute). 3.tig .mlSrieeoreoe Note: All " o e resources must specify a f c o yparameter with o g g o u . s f i p .RPCProvider handlerClass.RPCProvider handlerClass. Please check the Lifecycle and activation section for details. This parameter specifies a space or comma separated list of method names that can be called via SOAP. This is useful for restarting some tasks. Depending on the R s u c H m implementation different ye eoreoe options can be configured for the R s u c H m . For } example. Please see operation provider support section for details. ResourceHomeImpl parameters Name resourceKeyName Value <qname> Description This parameter specifies a QName of the resource key. s f j d .one.lbswr. at container startup without having to call the service.1. This parameter is similar to the allowedMethods standard Axis property but it specifies a Java class or an interface that is introspected to come up with a list of allowed methods that can be called remotely on the service.lbswr.

<eorenm=cce rsuc ae"ah" tp=oggou..3.. The "cacheLocation" parameter value is the JNDI name of the cache resource: <evc nm=Cutrevc" srie ae"oneSrie> <eorenm=hm"tp=.sfuiscceLUah" ye"r. When a . the same installation can be used to run different containers each with different configuration.sd sgSaitcTres to which the usage statistics of various components will be sent to. This for example can cause the state of the resource to be reloaded from disk on each call. The targets to which the usage statistics are sent to are configured via the u a e t t s i s a g t parameter defined in the < l b l o f g r t o >section sgSaitcTres goaCniuain of the $ L B S L C T O / t / l b s w r _ o e s r e . . 3. <rsuc> /eore <srie /evc> Please note that once the object is removed from the cache it is still up to the JVM to actually reclaim the object. A basic LRU (least recently used) cache implementation is provided.sfjd.2.lbswr. Configuring Resource Cache If ResourceHomeImpl is configured with resource class that implements the PersistenceCallback interface it will store the resource objects wrapped in Java SoftReference. .gar file is deployed.ah.globus..RCce> ..Cache interface. <aaee> prmtr <aecceoain/ae nm>ahLcto<nm> <au>aacm/n/evcsCutrevc/ah<vle vlejv:opevsrie/oneSriecce/au> <prmtr /aaee> .wsrf.e v r c n i . thus reducing the memory usage.> rsuc ae"oe ye". Once the cache resource entry is defined add the "cacheLocation" parameter to the service home resource. if not specified a default port will be ot:ot assumed). . ServiceResourceHome This implementation does not accept any special parameters. The same cache resource can be reused in different services but usually one cache per service will be configured. Defaults to 1 minute Optional cacheLocation <jndi path> This parameter specifies the JNDI location of the resource cache for this resource home. That allows the JVM to automatically reclaim these resource objects.2.2.lbswr. To configure a cache for ResourceHomeImpl first define a cache resource entry in JNDI: <eorenm=cce rsuc ae"ah" tp=oggou. The "timeout" parameter (in ms) is used to specify the idle time of the resource object before it is removed from the cache.sfuiscceLUah" ye"r. This is used to ensure that right type of resource object is added to resource home and to instantiate the right object if the resource supports persistence. Since the JVM can decide to reclaim these objects at any point.. Usage Statistics Configuration Java WS Core container and other GT services are configured to send out usage statistics.p o i eoption can be specified to deploy the configuration files under a specific profile name.o f g w d file.2. r : 8 0 sg-tt. The u a e t t s i s a g t parameter specifies a space separated list of targets GOU_OAINecgou_sfcr/evrcni.tl.lbswr.cache.utils. To prevent the JVM from reclaiming the resource objects so quickly a cache can be setup up to hold direct references to these objects. Each target is of form: h s [ p r ](port is optional.niBaFcoy/au> vleoggou.enatr<vle <prmtr /aaee> <aaee> prmtr <aetmot/ae nm>ieu<nm> <au>200/au> vle100<vle <prmtr /aaee> <rsucPrm> /eoreaas <rsuc> /eore In this case a LRU cache is configured.2. s dand/or GOU_OAINec<a.2. Configuration Profiles Configuration profiles allow for the same Java WS Core installation to have multiple configurations. a . Other cache implementations can be used as long as they implement the org. a e .ah. That is. Please see Configuring Resource Cache below for details. comment it out. To disable sending of the usage statistics remove this parameter.2.2.1. 3. or remove all of its values.d/poienm>sre-ofgwd .RCce> <eoreaas rsucPrm> <aaee> prmtr <aefcoy/ae nm>atr<nm> <au>r. By default usage statistics are sent to u a e s a s g o u .tl. . <rsucPrm> /eoreaas <rsuc> /eore .4. Please see the usage statistics section for more information. If the profile name is specified. 3. Required sweeperDelay <long> Optional." <eoreaas rsucPrm> . 3. sometimes a resource object can be reclaimed between two subsequent invocations on the same resource. This parameter specifies how often the resource sweeper runs in milliseconds.1.lbsog41. Drfl the deploy operation will drop the configuration file as $ L B S L C T O / t / g r i > < r f l .resourceClass <class> This parameter specifies the classname of the resource object.2.

These commands are documented in the Java WS Core Command Reference. In particular you will tma_ot/ofsre. a e < a e can be specified to set the name of the web Deapnm=nm> application under which the installation will be deployed. 4. By default on Sun JVMs a 64MB maximum heap size is used.TPSreSceFcoy poy"pt/opoyfl" rx=/aht/rx/ie cr=/aht/etfct/ie et"pt/ocriiaefl" ky"pt/opiaekyfl" e=/aht/rvt/e/ie ccrdr"pt/oc/etfctsdrcoy/ aeti=/aht/acriiae/ietr"> <Cnetr /onco> In the above the p o y c r .lbstma. Recommended JVM settings for the Java WS Core container It is recommended to increase the maximum heap size of the JVM when running the container. the standalone container can be started with a . k yand c c r d rattributes are optional.n i c n i .r f l option to load configuration files in a specific profile. 4.e v roption on Sun JVMs enables a server VM sre which can deliver better performance for server applications.1. The configuration profiles can also be created by hand simply by copying and/or renaming GOU_OAINec<a.1. a e . There are also helper programs (available only with the full GT installation) to start and stop the container detached from the controlling terminal (globus-startcontainer-detached and globus-stop-container-detached).i> n f hr/lbswr_omntma/octxl elyeueoct Doctdr<octdr Where <tomcat. It is also recommended to experiment with other JVM settings to improve performance.onco.1. sf The d p o S c r T m a task will update an existing Tomcat deployment if Java WS Core was already deployed under the specified web application name. Add a HTTPS Connector in the <Service name="Tomcat-Standalone"> section and update the parameters appropriately with your local configuration: <onco Cnetr casae"r. Example: Xx $stn GOU_PIN -m52 eev LBSOTOS Xx1M $$LBSLCTO/i/lbssatcnanr GOU_OAINbngou-tr-otie The above example will make the container start with maximum heap size set to 512MB. To undeploy a service use globus-undeploy-gar. Also. In addition to the above deployment step you will also need to modify the Tomcat < o c t r o > c n / e v r x lconfiguration file.x 1.aaiacnetrht.1.m JVM option. Java WS Core container The standalone Java WS Core container can be started and stopped with the provided globus-start-container and globus-stop-container programs.aaiantHTSevroktatr" lsNm=oggou. GOU_OAINecgou_sfcr/ni-ofgxl Once a configuration profile is created. Each configuration profile should duplicate the contents of $ L B S L C T O / t / l b s w r _ o e s r e .tpHtCnetr lsNm=ogaah. et e aeti rx et e mutually exclusive.pcectln.sd and $ L B S L C T O / t / l b s w r _ o e j d r c n i .e. These commands are documented in the Java WS Core Command Reference.w b p . . Important . Furthermore.octctln. elyeueoct The r d p o S c r T m a task can be used instead to overwrite the existing deployment. the p o yand the combination of c r and k yattributes are rx. Also.i=tma. poie 4.dir> is an absolute path to the Tomcat installation directory. 4. 4.o f g w d GOU_OAINecgou_sfcr/evrcni. m in order to have the basic functionality work properly.2.m dpoScrTma -tma.2. Deploying into Tomcat To deploy a Java WS Core installation into Tomcat run: $c $LBSLCTO d GOU_OAIN $at.d/poienm>jd-ofgxl the configuration files appropriately.m need to add the following configuration entries: Tomcat 4.tponco" pr=84"mnrcsos""mxrcsos"5 ot"43 iPoesr=5 aPoesr=7" atetct=tu"scr=tu"shm=hts uhniae"re eue"re cee"tp" ealLous"re acpCut"0 dbg"" nbeokp=tu" ceton=1" eu=0> <atr Fcoy casae"r. For example. the copied files in Tomcat might have different permissions then the originals. the .saegou_sfcmo/octtma. Deploying The Globus services can be run either in the standalone Java WS Core container that is installed with GT. eelyeueoct Note Please note that during deployment a subset of the files from Java WS Core installation is copied into Tomcat.1. m . or deployed into Tomcat. The maximum heap size can be set using the .$ L B S L C T O / t / g r i > < r f l . By default "w r " web application name is used. Deploying and undeploying services To deploy a service into Java WS Core container use the globus-deploy-gar tool.

. k yand c c r d rattributes are optional.. refer Security Descriptor.x 1. > section: <av casae"r. Furthermore.0.TPVle5/ Vle lsNm=oggou.TPVle/ Vle lsNm=oggou. the p o yand the combination of c r and k yattributes are rx.5. 2. refer Security Descriptor.octctln.lbstma.ooentHTSonco" lsNm=oggou.aeTPSreSceFcoy poy"pt/opoyfl" rx=/aht/rx/ie cr=/aht/etfct/ie et"pt/ocriiaefl" ky"pt/opiaekyfl" e=/aht/rvt/e/ie ccrdr"pt/oc/etfctsdrcoy/ aeti=/aht/acriiae/ietr"> In the above the p o y c r .tp1Ht1Pooo" sceFcoy"r. 2.lbstma. Add a HTTPS Valve in the <Engine name="Standalone" .TPCnetr pr=84"mxhed=10 mnprTras"5 mxprTras"5 ot"43 aTras"5" iSaehed=2" aSaehed=7" atFuh"re uols=tu" dsbepodieu=tu"shm=hts ialUlaTmot"re cee"tp" ealLous"re acpCut"0 dbg"" nbeokp=tu" ceton=1" eu=0 poooHnlrlsNm=ogaah.tp1rtcl rtcladeCasae"r. i.e. if you run Tomcat on port 443 using HTTPS then the WSRF servlet entry should be modified as follows: <e-p> wbap ..The credentials and certificate configuration is used only by the connector and is not used by the rest of the web services stack in Globus Toolkit.octcyt.m For example. k yand c c r d rattributes are optional.octcyt.e. To configure credentials for use in the toolkit. et e aeti rx et e mutually exclusive.ooeht1.lbstma. <eve> srlt <eve-aeWRSrlt/eve-ae srltnm>SFeve<srltnm> <ipa-aeWR CnanrSrlt/ipa-ae dslynm>SF otie eve<dslynm> <eve-ls> srltcas . Furthermore.. refer Security Descriptor.avsHTSav"> Tomcat 5. Important The credentials and certificate configuration is used only by the connector and is not used by the rest of the web services stack in Globus Toolkit.aaiavle. > section: <av casae"r.octcyt.ooevle.. > section: <av casae"r. tma. Important The credentials and certificate configuration is used only by the connector and is not used by the rest of the web services stack in Globus Toolkit.octctln.ooentHTSonco" lsNm=oggou..ooevle.TPCnetr pr=84"mxhed=10 mnprTras"5 mxprTras"5 ot"43 aTras"5" iSaehed=2" aSaehed=7" atFuh"re uols=tu" dsbepodieu=tu"shm=hts ialUlaTmot"re cee"tp" ealLous"re acpCut"0 dbg"" nbeokp=tu" ceton=1" eu=0 poy"pt/opoyfl" rx=/aht/rx/ie cr=/aht/etfct/ie et"pt/ocriiaefl" ky"pt/opiaekyfl" e=/aht/rvt/e/ie ccrdr"pt/oc/etfctsdrcoy/ aeti=/aht/acriiae/ietr"> In the above the p o y c r .aaiantBsHTSevroktatr" oktatr=oggou.lbstma. Add a HTTPS Valve in the <Engine name="Catalina" .e. et e aeti rx et e mutually exclusive.e.TPVle/ Vle lsNm=oggou. the p o yand the combination of c r and k yattributes are rx.x 1. Add a HTTPS Connector in the <Service name="Catalina"> section and update the parameters appropriately with your local configuration: <onco Cnetr casae"r.avsHTSav5"> Also. . To configure credentials for use in the toolkit.lbstma. 2.lbstma.octcyt. To configure credentials for use in the toolkit. Add a HTTPS Connector in the <Service name="Catalina"> section and update the parameters appropriately with your local configuration: <onco Cnetr casae"r.i>wbpswr/E-N/e.. you may have to edit < o c t d r / e a p / s f W B I F w b x lif you are running Tomcat on a non-default port. not using port 8443 (HTTPS).avsHTSav"> Tomcat 5.pcecyt. Add a HTTPS Valve in the <Engine name="Catalina" .

a of a Java WS Core installation do: wr $c $LBSLCTO d GOU_OAIN $at.i>cmo/i tma. a and $ L B S L C T O / i / o m n . Similarly. .2.i>cmo/i/xsuljr $bnsatp i/tru 4.a e LSPT=tma. first undeploy the service from a regular GT installation using globusundeploy-gar tool and then deploy the GT installation into Tomcat. copy < o c t d r / e a p / s f W B GOU_OAINlbcmoslgigjr tma.i>cmo/lse/ Tomcat 5.i>wbpswr/EI F c a s s l g j p o e t e file to < o c t d r / o m n c a s s directory.2.2+. To execute the test do the following: 1. The debugging settings will tma.xseve <srltcas /eve-ls> <ntprm ii-aa> <aa-aedfutrtcl/aa-ae prmnm>ealPooo<prmnm> <aa-au>tp<prmvle prmvlehts/aa-au> <ii-aa> /ntprm <ntprm ii-aa> <aa-aedfutot/aa-ae prmnm>ealPr<prmnm> <aa-au>4<prmvle prmvle43/aa-au> <ii-aa> /ntprm <odo-tru>re/odo-tru> la-nsatptu<la-nsatp <srlt /eve> .r . tma.2. Deploying and undeploying services To deploy a service into Tomcat. Testing To execute Java WS Core tests first ensure Ant is configured with JUnit (To install JUnit with Ant copy the junit.x Copy $ L B S L C T O / i / o m n .2.i>wbpswr/E-N/lse/ only affect the web application code. Enabling Log4J debugging Tomcat 4.2. first deploy the service into a regular GT installation using the globus-deploy-gar tool and then deploy the GT installation into Tomcat (as described in Section 4. Note Some GT services may not work properly in Tomcat.2.otie. Tomcat log files Please always check the Tomcat log files under the < o c t d r / o sdirectory for any errors or exceptions.i>wbpswr/E-N/i/ directory.ie Where <war.2.o g n .2.i>cmo/lse/ < o c t d r / o m n c a s s directory appropriately. a files to < o c t d r / o m n l bdirectory.i>cmo\i\xsuljr >bnsatp i\tru On Unix/Linux (csh/tcsh): $c <octdr d tma..3. Enabling local invocations To enable local invocation in Tomcat you must add a i . 5.x Copy $ L B S L C T O / i / o 4 .lbswr.x.1. Start the standalone container with .a eev LSPT tma.i> >stCASAH<octdr\omnlbai-r. nosd 4. in some cases the x l n j rmust be a aa. Also.sfcnanrAiSrlt r.i> $stn CASAH<octdr/omnlbai-r. 4. 4.2.5.a placed in the e d r e directory of the container.2. xsuljr For example on Windows: >c <octdr d tma.4.o g n .rpris tma. . 5. Please note that deploying a w rfile might not be enough to have a working Java WS Core deployment.jar found in the JUnit distribution to the $ANT_HOME/lib directory). “Deploying”). a to the CLASSPATH before starting Tomcat.1. tma. Then configure the Log4j configuration file in N/lse/o4. a files to < o c t d r / e a p / s f W B I F l b GOU_OAINlblgj128jr GOU_OAINlbcmoslgigjr tma. .saegou_sfcmo/octtma. Debugging 4. Creating WAR file To create a .i>lg 4. <wbap /e-p> Note We recommend running Tomcat with Java 1. The debugging settings will affect all the code in all web applications. Then configure the Log4j configuration file in < o c t d r / e a p / s f W B I F c a s s directory appropriately.1.m wr-wrfl=wrfl> n f hr/lbswr_omntma/octxl a Da.ie<a.oggou..file> specifies the absolute path of the war file. to undeploy a service.4.0.o e argument: nsc . For example.

g aa jv -lspt $LSPT -jv. Permissions of service configuration files The service configuration files such as jndi-config. you can set the G O U _ P I N environment LBSOTOS property as described above.2. e u i y e dsystem property can be set to configure a different entropy source.wsdd (located under $ L B S L C T O / t / g r /directory) may contain private GOU_OAINec<a> information such as database passwords.sd work correctly on all platforms and this does not apply to any other configuration files.a DaiTssnytu 4. Please see the WS Authentication & Authorization section for details. g o u .e o t /directory.oPorm aa casah CASAH Daascrt. There are two ways to prevent this from happening: 1. 7. However. GOU_OAINsaegou_sfts/et/etrprs Please see the developer guide for more information on running the tests and the testing infrastructure. Sometimes the machine can run out of entropy and applications dvrno (such as the container) using the / e / a d mdevice will block until more entropy is available.a Det.euiyedfl:dvuadm or stn GOU_PIN -jv. If the ShutdownService or the container is lbsso-otie configured with separate private key and certificate files (usually / t / r d s c r t / o t i e c r .saegou_sfts/utssxlrnevr\ n f hr/lbswr_etrnet. Ensure that the entire ~ . /gou/esse /gou/esse 6.e m otiepoypm Alternatively.t p c n a n rfails with an authorization error lbsso-otie By default g o u .g system property and pass it to g o u .e eev 59UE_RX otiepoypm $gou-tpcnanr lbsso-otie $ustn X0_SRPOY neev 59UE_RX $r cnanrrx. 6.euiyedfl:dvuadmm.e -u cnanrrx.g=ie/e/rno The same issue can also affect client programs. For Sun JVMs a j v .e) following to stop the container: $gi-rx-nt-et/t/rdscrt/otiecr. Configure appropriate a l w d e h d or a l w d e h d C a sparameter in the service deployment descriptor (please see Java WS Core Configuration loeMtos loeMtosls for details).euiyedfl:dvuadm eev LBSOTOS Daascrt. To set the dvuadm aascrt. For example: aascrt. Run the interoperability tests: $at.m evrcni. Permissions of persistent data The services using subscription persistence API or other basic persistence helper API will store all or part of its persistent data under the ~ . Invocation of non-public service functions A client can potentially invoke a service function that is not formally defined in the WSDL but it is defined in the service implementation class.2.o t i e hangs during startup lbssatcnanr By default Sun 1. If some tests failed examine the test results in the $ L B S L C T O / h r / l b s w r _ e t t s s t s .m uSre -tssjr$LBSLCTO/i/sfts_ntjr-bscetOl=re Det. Define all service methods in your service class as either p i a eor p o e t d rvt rtce. if you are using a custom script or directly launching a program using the j v command line.e ot otiepoypm $stn X0_SRPOYcnanrrx.1.a=GOU_OAINlbwr_etitrpjr 3.1.g=ie/e/rno ypcaeForga Note: This does not apply to Windows machines. If you are running a client program with a GT generated script. l b s p r i t ddirectory.3. .a=GOU_OAINlbwr_etui.o f g x land s r e .xml or server-config. Troubleshooting 7.t r .4.g=ie/e/rno xot LBSOTOS-jv. 6. the ShutdownService can be configured with a separate gridmap file to allow a set of users to stop the container. g o u . 7.$c $LBSLCTO d GOU_OAIN $bngou-tr-otie -oe i/lbssatcnanr nsc 2.t r . this might not nicni. e and / t / r d s c r t / o t i e k y p m do the ecgi-euiycnanretpm ecgi-euiycnanre.o t i e script do the following: lbssatcnanr epr GOU_PIN=Daascrt. One workaround for this issue is to configure the JVM to use dvrno / e / r n o (non-blocking) device instead. e u i y e dsystem property explicitly on the j v command line.t p c n a n rmust be executed with the same credentials as the container it is running with.o f g w d files as user readable only. Run the unit tests: $at.e \ rdpoyii cr ecgi-euiycnanretpm -e /t/rdscrt/otiekypm\ ky ecgi-euiycnanre. The deployment process automatically sets the permissions of the j d . etc.saegou_sfts/utssxlrnevr\ n f hr/lbswr_etrnet.m uSre -tssjr$LBSLCTO/i/sfts_neo. Ensure that these configuration files are only readable by the user that is running the container. However. make sure to set the aa j v .x+ JVMs are configured to use / e / a d mdevice as an entropy source.akg. Security Considerations 6. l b s p r i t ddirectory is only readable by the user running the container. 2.

o k t x e t o : I v l d a g m n o c n o a s g r q e t d a d e s aantSceEcpin nai ruet r ant sin euse drs If you see the "j v .ooevle.aa72 t aaui. General troubleshooting information In general. Either install the JAAS library or upgrade to J2SE 1. j v .container startup list of services . if you want to investigate a problem on your own please see the Debugging and Logging section for details on how to turn on debugging.e u option that will display more detailed error messages. packet version. e .x ocretoiiainxeto If the following exception is visible in the Tomcat logs at startup it might cause the H T S a v to fail: TPVle jv. Please include as much as detail about the problem as possible.avsHTSav. dbg searching the mailing lists such as gt-user@globus.0.ooeeus.ocretoiiainxeto a jv. This is a Tomcat bug.org [privacy statements] For technical support or questions about Globus software.org (before posting a message) can also be very fruitful. For questions or feedback about this website: webmaster@globus. please see the Java WS Core System Administrator's Guide section on Usage Statistics Configuration for instructions.evrDfutBaRpstr.eAtiueCytRqetaaejv:5) a oggou. servlet.0. Globus Alliance.aha.agNlPitrxeto aaln. .oct. timestamp.uloneEcpin a ogaah.tlHsMpEtytrtrnx(aha.e.5. 7. please see our policy statement on the collection of usage statistics.3.aha$ahtrtrnxEtyHsMpjv:8) a jv.aa9) t r.3+) If you wish to disable this feature. o k t x e t o : I v l d a g m n o c n o a s g r q e t d a d e s error in the container log or on the client side try aantSceEcpin nai ruet r ant sin euse drs" setting the following property: $epr GOU_PIN=-jv.ln(ealMeneoioyjv:6 t xjsre. Keep restarting Tomcat until it starts without the C n u r n M d f c t o E c p i nor switch to a different version of Tomcat.octcyt. These errors might occur when running with J2SE 1.0. Globus. 8. ocretoiiainxeto 7.etnr(aha.aha.3+) container uptime (4.6. servlet.standalone.xoeHTSav.aa31 t r.tlHsMpptlFrraeHsMpjv:2) t aaui. a g N C a s e F u d r o : j v x s c r t / .etHsMpjv:2) a jv. including the error stack traces.4.container shutdown list of activated services .tlHsMpHsIeao.service names only On container shutdown: container id .oct.rfrP4tc=re xot LBSOTOS"DaantpeeIvSaktu" 7.uAloCet(aha.org or gt-dev@globus.aha$nrIeao.lbstma.pcecyt.random number container type .aa5) The H T S a v might fail with the following exception: TPVle jv.aa44 a jv.aa17) t r.service names only (4.ooetma5CytRqetsttrbt(ooeeus. e . please note that most of the command line clients have a .3. C n u r n M d f c t o E c p i nin Tomcat 5.olsDfonErr aa/euiy. and the source IP address): On container startup: container id .ooetma5CytRqetaaesttrbt(ooeeusFcd.4.eAtiueCytRqetjv:42 a ogaah.TPVleeps(TPVlejv:9 These exceptions will prevent the transport security to work properly in Tomcat.aa84 t aaui. Also. Finally.pcecyt.standalone. visit our technical support page.aa66 a m4. or unknown event type . Also.. Programs fail with j v .tlCnurnMdfctoEcpin aaui.tlHsMpcoeHsMpjv:5) t aaui. and Globus Toolkit are trademarks held by the University of C hicago.ooeeusFcd. Also.x or higher.1 and the JAAS library is not installed.7. if you think you have found a bug please report it in our Bugzilla system.ealMeneoioycoeDfutBaRpstr.random number container type . or unknown event type . errors aaln. Usage statistics collection by the Globus Alliance The following usage statistics are sent by Java WS Core by default in a UDP packet (in addition to the Java WS Core component code.ln(aha.

Sign up to vote on this title
UsefulNot useful