[ogsa-hpcp-wg] UVA SC06 interop endpoint

[Peter G. Lane]

Here's my concern: if we don't all agree that EPRs are the standard way of referencing a BES-factory 
endpoint, then how can I be guaranteed that my service (which will definitely require an EPR) will 
be interoperable? Besides, the Activity is referenced by an EPR, so I don't understand what the 
problem is with referencing the factory in the same manor.

Peter

Glenn Wasson wrote:
> Peter,
> 
> 	Not everyone needs an EPR to contact the service. 
> 
> Glenn
> 
> -----Original Message-----
> From: Peter G. Lane [mailto:lane at mcs.anl.gov] 
> Sent: Friday, October 13, 2006 12:10 PM
> To: Glenn Wasson
> Cc: ogsa-hpcp-wg at ggf.org
> Subject: Re: [ogsa-hpcp-wg] UVA SC06 interop endpoint
> 
> Glenn Wasson wrote:
>> Fellow interopers:
>>
>> I mentioned on the call that I have 2 endpoints available, but one of them
>> is still a little raw, so I'll just give out the URL for one and the
> second
>> will follow next week.
>>
>> The URL is https://wincluster1.cs.virginia.edu/HPCP/HPCPService.asmx 
> 
> Endpoints should be posted as EPRs, not URLs.
> 
> Peter
> 
>> The service is a .NET2.0/WSE3 frontend and MS CCS backend.
>>
>> The CA cert for the host is available at:
>> https://www.pki.virginia.edu/ca/rootcert/rootcert.cer
>>
>>
>> Here's an example JSDL doc that can be used:
>>
>> <ActivityDocument>
>>    <JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl">
>>        <JobDescription>
>>           <JobIdentification>
>>              <JobName>JobName</JobName>
>>              <JobProject>JobProject</JobProject>
>>           </JobIdentification>
>>           <Application>
>>              <ApplicationName>ipconfig</ApplicationName>
>>              <HPCProfileApplication
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="TaskName"
>> xmlns="http://schemas.ggf.org/jsdl/2006/07/jsdl-hpcp">
>>                  <Executable>ipconfig.exe</Executable>
>>                  <Argument>/all</Argument>
>>                  <Output>ipconfig.txt</Output>
>>                  <Error>ipconfig_err.txt</Error>
>>                  <WorkingDirectory>\\wincluster1\head_node_share\Dev\HPC
>> Profile\HPCP_Out</WorkingDirectory>
>>               </HPCProfileApplication>
>>           </Application>
>>           <Resources>
>>              <TotalCPUCount>
>>                 <UpperBoundedRange>1</UpperBoundedRange>
>>                 <LowerBoundedRange>1</LowerBoundedRange>
>>              </TotalCPUCount>
>>            </Resources>
>>        </JobDescription>
>>    </JobDefinition>
>> </ActivityDocument>
>>
>> *** You can view the resulting output at
>> http://wincluster1.cs.virginia.edu/HPCP-Out/ipconfig.txt
>>
>>
>> All methods are available on this service (though the return from
>> GetFactoryAttributesDocument is a bit sparse). Also, any errors should
>> return SOAPFaults, though their format may be idiosyncratic to my
>> implementation. 
>>
>>
>> Glenn
>>
>> --
>>   ogsa-hpcp-wg mailing list
>>   ogsa-hpcp-wg at ogf.org
>>   http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg
>>
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3804 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.ogf.org/pipermail/ogsa-hpcp-wg/attachments/20061013/7b5267ae/attachment.bin