What is Best option to use ServiceContext with DFS in .net

PritamKadam

Hi DFS Gurus,

I am implementing DFS WebServices SP3 with C# .net 3.5. I have added WSDL link to web reference and using .net WCF. I have managed to write a SOAP message header part on fly. There are two options I can create service context on server. 1) Register service context and use token next time to call services. OR 2) Do NOT register service context and use username and password everytime you call services.

I am prettymuch new to DFS and documentum.

1) Register service context

----------------------------------------------

ServiceContext

serviceContext = new ServiceContext();

RepositoryIdentity repositoryIdentity = new RepositoryIdentity();repositoryIdentity.repositoryName = docbase;

repositoryIdentity.userName = userName;

repositoryIdentity.password = password;

serviceContext.Identities = new Identity[1];serviceContext.Identities[0] = repositoryIdentity;

token = reg.register(serviceContext,

null);

ContextRegistryHeader

crh = new ContextRegistryHeader();crh.Token = token;

OperationContext.Current.OutgoingMessageHeaders.Add(crh);

----------------------------------------------

Here I am planning to save this token in ASP.net cookies, so I can use it later on. But not sure about how long registered service context will stay alive on server, So I can kill my cookie after that period.

====================

2) DO NOT register service context  // This is actually I prefer to use services.

----------------------------------------------

ServiceContextHeader

scx = new ServiceContextHeader();

RepositoryIdentity repositoryIdentity = new RepositoryIdentity();repositoryIdentity .repositoryName = docbase;

repositoryIdentity .userName = userName;

repositoryIdentity .password = password;

scx.AddRepositoryIdentity(repositoryIdentity);

OperationContext

.Current.OutgoingMessageHeaders.Add(scx);

----------------------------------------------

I have tested this snipet with SearchServices and sometime it works and sometime it throw error : Authorization failed, Could not find Identities in Service context.

I was testing with ObjectServices and everytime getting an error: Authorization failed, Could not find Identities in Service context.

Any one who worked with DFS webservices with .net please help me out.

abc123

1) You are able to custom the expiration of service context in dfs-runtime.properties:

dfs.crs.cache_expiration_after_x_minutes Indicates the expiration timeout for ServiceContexts in the server-side cache
dfs.crs.perform_cleanup_every_x_minutes How often expired service contexts are being removed from the cache to free up resources

For example, if you set them with 20 min and 60 min respectively, ideally, the longest alive time of the service context is 80 minutes.

2) Not sure which version of DFS you are working on. In some specific version (i.e. 65SP3), the security header requires the format with:

<wsse:BinarySecurityToken QualificationValueType="http://schemas.emc.com/documentum#ResourceAccessToken"                    
        EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"                    
        xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"            
        wsu:Id="RAD">

To choose registered token or username/password, it depends on your application requirements.

There are two benefits to registering the service context. The first benefit is that services can share a registered context. This minimizes over the wire traffic since the consumer does not have to send service context information to every service it calls.
The second benefit occurs when a consumer calls a service and passes in a delta modification to the service context. The DFS client runtime figures out the minimal amount of data to send over the wire (the modifications) and the server runtime merges the delta modifications into the service context that is stored on the server.

To get more information, please refer to DFS develop guide.

- William

1) Register service context
Here I am planning to save this token in ASP.net cookies, so I can use it later on. But not sure about how long registered service context will stay alive on server, So I can kill my cookie after that period.2) DO NOT register service context  // This is actually I prefer to use services.
I have tested this snipet with SearchServices and sometime it works and sometime it throw error : Authorization failed, Could not find Identities in Service context.I was testing with ObjectServices and everytime getting an error: Authorization failed, Could not find Identities in Service context.Any one who worked with DFS webservices with .net please help me out.