KeystrokeEsbNet Forum Rss Feed

New Post: Dynamic custom service parameters

minas — Fri, 03 Apr 2009 11:05:06 GMT

Hi Brian,
TIP:
As a general reference, you can use the ESB Management Console code as sample code.

For what you want - a simple name/value pair...,

there's a 1-liner you can use to set the value...

oEnv.SetCustomParam("productABC", "MN")

...and send the request...

oServer.ProcessMsgSync(oEnv.XML, sXMLResponse)

...and to get the value in your handler...
sProdABCValue = oEnv.GetCustomParam("productABC")

Here's an excerpt from the ESB Management Console:

Dim oServer As New ESB.Core.Adaptors.Transport.RequestHandlerProxy.Sender(Session("SendUrl"), Session("TransportType"), Session("TransportClientEndPointName"))
Dim oTimer As New ESB.Core.Util.Timer
oTimer.StartTimer()
Dim sXMLResponse As String
'Add in a Custom Parameter which tells the Send Transport Adaptors (if they choose to honour it...)
'how many times to execute this request at their level
'Note that they run their own loop, independent of the one in here.
'That ensures all connection and data setup times are removed from those timings
'Use the GetBaseContext.m_sExecutionTime to get those timings...

Dim oEnv As New ESB.Core.XMLSchemaClasses.ESBEnvelope.Envelope
oEnv.XML = txtXMLRequest.Text

oEnv.SetCustomParam(ESBConstants.C_sClientNumExecutionTimes, txtNumExecutionTimesAdaptor.Text)

'++Make the call
For nExecutionTimes As Integer = 1 To txtNumExecutionTimes.Text

oServer.ProcessMsgSync(oEnv.XML, sXMLResponse)

'--Make the call
Next
oTimer.StopTimer()
txtXMLResponse.Text = sXMLResponse
Dim oXMLUtil As New ESB.Core.XMLSchemaClasses.XMLUtil
txtXMLResponse.Text = oXMLUtil.PrettyFormatXML(sXMLResponse)
txtResponseTime.Text = oTimer.Duration() & ";" & GetBaseContext.m_sExecutionTime

Also, for Configured Services, in the Service Pipeline Configuration, you can specify a Custom Parameter for your handlers [these are in the Multi-Level-Overrides, so you can take advantage of the Data Inheritance feature here too...]
The example below specifies a handler [used for stubbing out the service implementation for clients during the dev. process] that returns a particular file.
So, you can define your service [in config only], have it return a payload from a file by configuring a standard handler, and specify for that particular service, which payload to return.
The next service you define [or use the context in the request envelope to vary the responses based upon a set of context strings used for testing etc.] can use the same config code, just change the file to be returned...

<PipelineMapSection name="Testing - Generic SOAP Transport Adaptor">
<PipelineEntry> <ResolveNameEntry> <ContextEntry>
<Context>http://ESB.Keystroke.com.au/ESB/wsdl/.ProcessMsgSync</Context> <ResolveName>ProcessMsgSync</ResolveName> <PipelineID>1</PipelineID> <ProcessInParallel>0</ProcessInParallel> <ResponseIsRequestForNextPipelineItem>1</ResponseIsRequestForNextPipelineItem>
<MultiLevelOverrides>
<TransactionComponent>ESB.Testing.TestTxns.ReturnSpecifiedFileHandler</TransactionComponent> <ComponentServer suffix="yes">Base\Solutions\Main\Testing\ESB.Testing.TestTxn\bin\ESB.Testing.TestTxns.dll</ComponentServer>
<Custom> <ParamName>ReturnSpecifiedFile</ParamName>
<ParamValue>C:\ESB\DevServer2\Source\ESB\Base\Solutions\Main\Management\ESB.Management.Portal\Testing\XMLRequests\ESBCore\ESBTest15_Sync.xml</ParamValue>
</Custom>
</MultiLevelOverrides> .....

New Post: Dynamic custom service parameters

bmatchey — Thu, 02 Apr 2009 20:37:35 GMT

Is there a way to send custom service parameters in the message header from the client?

I am able to create them in the message envelope on the client, but they are not there in the service. It appears the service is reading the header portion from configuration instead. Is that right?

Here's how I had the client inject custom parameters:

        private void invokeService(ProcessMsgClient client)
        {
                ESBMessage request = new ESBMessage();

                // Create request message.
                XmlDocument reqXML = new System.Xml.XmlDocument();
                reqXML.InnerXml = txtPayload.Text;
                createCustomParameters(reqXML, "productABC", "MN");
                request.EnvelopeXML = reqXML.DocumentElement;

                // Submit request.
                AsyncCallback resultHandler = new AsyncCallback(ServiceCompleted);
                client.BeginProcessMsgSync(request,resultHandler,null);
        }

        private void createCustomParameters(XmlDocument reqXML, String aProductId, String aStateCd)
        {
            XmlNamespaceManager nsmgr = new XmlNamespaceManager(reqXML.NameTable);

            XmlElement root = reqXML.DocumentElement;
            nsmgr.AddNamespace("df", root.NamespaceURI); // Add a default namespace reference.

            XmlNode customServiceNode = root.SelectSingleNode("./df:header/df:service/df:custom", nsmgr);
            if (customServiceNode == null)
            {
                XmlNode serviceNode = root.SelectSingleNode("./df:header/df:service", nsmgr);
                customServiceNode = reqXML.CreateNode(XmlNodeType.Element, "custom", serviceNode.NamespaceURI);
                serviceNode.AppendChild(customServiceNode);
            }

            // Add product id parameter.
            XmlNode productIdNode = reqXML.CreateNode(XmlNodeType.Element, "productId", serviceNode.NamespaceURI);
            productIdNode.InnerText = aProductId;
            customServiceNode.AppendChild(productIdNode);

            // Add state parameter.
            XmlNode stateNode = reqXML.CreateNode(XmlNodeType.Element, "stateCd", serviceNode.NamespaceURI);
            stateNode.InnerText = aStateCd;
            customServiceNode.AppendChild(stateNode);
        }

New Post: Configured adaptor

bmatchey — Fri, 27 Mar 2009 20:29:49 GMT

I got past the Server Application Unavailable error.
It turns out the event log was full and it stopped ESB.NET from completely processing the request.

The event it was trying to log was:
Could not invoke start async logger URL : http://localhost/ESB/Source/AsyncLogger/MsmqToMsSql.aspx. Service URL invoking is:http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc/Default

I thought I had SQL logging turned off, but maybe it isn't.

Anyway, I have confirmed that my configured adapter is firing.

Thanks for your help, Minas. (BTW: I'm still interested in your comments of the email I sent you.)

New Post: Configured adaptor

bmatchey — Fri, 27 Mar 2009 18:22:16 GMT

Ok, I've gotten a little further.
My problem was a bit of a misunderstanding on how best to do things. In my first attempt, I read through all the documentation I could find and tried to create files manually based on what I read.
There's a much easier way as Minas has eluded to above.

To hook up an existing service to ESB.NET, my advice to you is to start in ServicePipeline.config.
You will find this file at \ESB.NET\6.2.9.0_x64\Source\ESB\Base\Solutions\Main\Configuration\XMLConfigFiles\ServicePipeline.config.

Create a "ESB.Core.Pipeline/Config/PipelineConfig/Vertical/PipelineMapSection" node for your service (see example below).
Save the ServicePipeline.config changes and browse to "Service Pipeline" in ESB Management console.
Click View BSDL on your service. This will create the BSDL file shown at the top to the resulting page.
\ESB.NET\6.2.9.0_x64\Source\ESB\Base\Solutions\Main\Management\ESB.Management.Portal\ServiceDefinitions\ServiceDefinition.com.fsc.MyServiceESBNETAdaptor.1.0.0.0.xml
Modify this file in a text editor, adding a "ServiceDefinition/Service/Request/Document/Schema/Url" node that points to your service handler's schema.
Save your changes, return to "Service Pipeline" in ESB Management console and try the "Sample Request" link on your service.
You should see an xml example that you can adjust and "Send Request". (This is still failing for me with an unhandled exception somewhere, but I believe the steps so far are proper. Minas, please verify and/or comment. Note: I have added the MyServiceHandler class to my service - extends ESB.Adaptors.Application.Workflow.ServiceBase -, but I am getting a Server Application Unavailable message and nothing in the Event log.)

Server Application Unavailable

The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

PipelineMapSection example:
                    <PipelineMapSection>
                        <PipelineEntry>
                            <ResolveNameEntry>
                                <ContextEntry>
                                    <Context>com.myDomain.MyServiceESBNETAdaptor.1.0.0.0</Context>
                                    <ResolveName>MyServiceRequestType::http://schemas.datacontract.org/2004/07/MyServiceESBNETAdaptor</ResolveName>
                                    <PipelineID>1</PipelineID>
                                    <ProcessInParallel>0</ProcessInParallel>
                                    <ResponseIsRequestForNextPipelineItem>0</ResponseIsRequestForNextPipelineItem>
                                    <MultiLevelOverrides>
                                        
                                        <RequestQ/>
                                        
                                        <TransactionComponent>MyServiceESBNETAdaptor.MyServiceHandler</TransactionComponent>
                                        
                                        <ComponentServer suffix="yes">\MyService\MyServiceESBNETAdaptor\bin\MyServiceESBNETAdaptor.dll</ComponentServer>
                                        
                                        <UseObjectBroker>0</UseObjectBroker>
                                        <ObjectBroker/>
                                        <ObjectBrokerServer/>
                                        
                                        <ValidateInputSchema>0</ValidateInputSchema>
                                        <ValidateOutputSchema>0</ValidateOutputSchema>
                                        <IgnoreInputSchemaValidationErrors/>
                                        <IgnoreOutputSchemaValidationErrors/>
                                        
                                        
                                        <Custom>
                                            <ParamName/>
                                            <ParamValue/>
                                        </Custom>
                                    </MultiLevelOverrides>
                                </ContextEntry>
                            </ResolveNameEntry>
                        </PipelineEntry>
                        <MultiLevelOverrides>
                            <RequestQ/>
                            <ComponentServer suffix="yes">C:\Projects\Services</ComponentServer>
                            <TransactionComponent> </TransactionComponent>
                            <Custom>
                                <ParamName> </ParamName>
                                <ParamValue> </ParamValue>
                            </Custom>
                        </MultiLevelOverrides>
                    </PipelineMapSection>

New Post: Configured adaptor

minas — Fri, 27 Mar 2009 11:41:10 GMT

1) Insight to your problem

I suspect the reason for this error is that the request message is not correctly formed. The configuration looks good.

i.e. It does not have the correct ResolveName and Context in the request, must match that of the Configuration.

<Context>com.MyDomain.MyService.MyServiceHandler1.0.0.0</Context>

<ResolveName>MyServiceRequestType::http://schemas.datacontract.org/2004/07/MyServiceESBNETAdaptor</ResolveName>

I suspect this is because you did not setup the BSDL with a Request Schema Root Element Name and Namespace.

As a result, when you click "Sample Request" (which creates the sample using the BSDL), it will not create a request message that invokes your service.

2)What to do to fix it

Option 1 [recommended] - Populate the BSDL supplying a valid schema name and namespace to match your request.

To do this:

i)From the service pipeline configuration page, select the "View BSDL" for the service.

ii)Near the top of the page, there's a Service Definition File Path tag with the path to the service definition next to it.

...something like:

C:\ESBDeploy\6\6.2.9.0_x64\Source\ESB\Base\Solutions\Main\Management\ESB.Management.Portal\ServiceDefinitions\ServiceDefinition.WindowsWorkflow3.0.StartCase2.ProcessWFTxn1.0.0.0.xml

Open up that file with a text editor, and change the bits in Red.

<?xml version="1.0" encoding="utf-8"?>

<ServiceName>WindowsWorkflow3.0.StartCase2.ProcessWFTxn1.0.0.0</ServiceName>

</DistinguishedServiceName>

<Name>MyServiceRequestType</Name>

<Namespace>http://schemas.datacontract.org/2004/07/MyServiceESBNETAdaptor</Namespace>

</Schema>

</Document>

</Request>

<ServiceProviderName>Keystroke IT Australia</ServiceProviderName>

</Service>

</ServiceDefinition>

</Services>

iii)Save the file & then generate the sample request again.

Option 2[if it all gets too hard] - Create a message manually and paste it into the Generic Request Sender page.

3)Useful background info

3.1) The Service Pipeline Manager runs & looks for matches, caches in hashtable etc.

The ConventionOverConfiguration functionality is simple a handler that runs at the end of the Service Pipeline (configured in the Pipeline) and look for scenarios where there was no Configured match in the Pipeline for a given request.

Once it detects this, it runs it's rules - Based upon a Convention, to detect whether the request can be handled using the Convention built into the ConventionOverConfiguration handler.

In this case, because the request sent did not match any configuration, the ConventionOverConfiguration handler decided to try & see if there was anything that would match it's convention that could satisfy this request.

4)Other recommendations

4.1)If you plan to not use the ConventionOverConfiguration feature for a particular instance, you should probably disable it to improve performance, as it will otherwise kick in needlessly.

If you plan to still use it in conjunction with the configured services, then leave it in.

4.2)It's great to hear that you're planning to build lots of services with ESB.NET.

Note that you can write/customize the ConventionOverConfiguration handler to meet your own requirements.

If you have an existing structure that has a rigid convention, then maybe this can be a way to minimize the amount of work you need to do to route the services through ESB.NET.

4.3)With that many services, I suggest you plan your federation strategy. For many reasons, you'd want to group your services into logical namespaces & probably related ESB.NET instances. This will greatly help with maintenance & overall availability/uptime.

Instances that map to namespaces are a great way to get up & running quickly. Override by re-routing requests [configure in a routing config for that service or request re-mapping if needed on a large scale etc.] on an as-need basis.

You can also modify the RequestHandlerProxy to have any routing logic conventions/configuration built into it to make life on the server side easier/cleaner if you need to [just keep this option in your back pocket in case you need it].

4.4)With the services you've got built, you can also look at having an interpreter handler run before/after each of your service to do any generic translation that needs to be done for each service you're invoking.

If you need any more guidance, email me on minas@optusnet.com.au.

HTH

Good luck

Cheers

Minas

New Post: File missing from 6.2.9.0?

minas — Fri, 27 Mar 2009 10:56:13 GMT

Hi,
1)Correct. The ESB.Adaptors.Envelopes.ESBMessageEnvelope.dll is missing. I'll fix that in the next release. Thanks.
2)You can just open up the .vbproj project and build it. Should all be good after that.
3)Note that this is NOT the default envelope. You can use the Default Envelope ESBEnvelope if you like to aid in your troubleshooting. The EBEnvelope ships with the core. The ESBMessageEnvelope ships as a standalone envelope & is an example of how to roll your own envelope...

New Post: File missing from 6.2.9.0?

bmatchey — Thu, 26 Mar 2009 21:37:02 GMT

In the configuration file \ESB.NET\6.2.9.0_x64\Source\ESB\Base\Solutions\Main\Configuration\XMLConfigFiles\ESB.Core.Envelopes.config, there is reference to a DLL that is not included in the install:
                <Envelope>
                    <ObjectName>ESB.Adaptors.Envelopes.ESBMessageEnvelope.ESBMessageEnvelope.ESBMessageEnvelopeProvider</ObjectName>
                    <AssemblyPath>Envelopes\ESB.Adaptors.Envelopes.ESBMessageEnvelope\bin\ESB.Adaptors.Envelopes.ESBMessageEnvelope.dll</AssemblyPath>
                    <SchemaPath>Envelopes\ESB.Adaptors.Envelopes.ESBMessageEnvelope\XMLSchemas\1.0.0.0\ESBMessageEnvelope.xsd</SchemaPath>
                    <SchemaRootElement>ESBMessageEnvelope</SchemaRootElement>
                </Envelope>

I believe this is why I am getting an error when attempting to build a configured adaptor.
When I try to 'Display Request' from the Generic Request Sender screen or I try to 'Sample Request' from the Service Pipeline screen, I get the error below.
Is ESBMessageEnvelope.dll supposed to be available or do I have something configured wrong?

Server Error in '/ESB/Source/Management' Application.

Could not load file or assembly 'file:///D:\Visual Studio\ESB.NET\6.2.9.0_x64\Source\ESB\Envelopes\ESB.Adaptors.Envelopes.ESBMessageEnvelope\bin\ESB.Adaptors.Envelopes.ESBMessageEnvelope.dll' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'file:///D:\Visual Studio\ESB.NET\6.2.9.0_x64\Source\ESB\Envelopes\ESB.Adaptors.Envelopes.ESBMessageEnvelope\bin\ESB.Adaptors.Envelopes.ESBMessageEnvelope.dll' or one of its dependencies. The system cannot find the file specified.

New Post: Configured adaptor

bmatchey — Thu, 26 Mar 2009 18:43:31 GMT

Hi,

I'm having trouble figuring out how to configure an adapter that is outside the ESB\LOBSystems folder.
The reason I don't want to use convention over configuration is that I have existing services that I want to plug in and want to retain my existing directory structure.
There will be thousands of services and I want to create a VS 2k8 C# template that can easily be added to wrap these services to expose them to ESB.NET.

Anyway, I've added a PipelineConfig/Vertical/PipelineMapSection node to \ESB.NET\6.2.9.0_x64\Source\ESB\Base\Solutions\Main\Configuration\XMLConfigFiles\ServicePipeline.config, but am currently getting an error when attempting to run a sample XML through:

System.Exception: Attempted to create object:com.MyDomain.rateRTMarket.rateRTMarketHandler1.0.0.0 in Assembly:

D:\Visual Studio\ESB.NET\6.2.9.0_x64\Source\ESB\LobSystems\ns\com.MyDomain.MyService.MyServiceHandler1.0.0\bin\com.MyDomain.MyService.MyServiceHandler1.0.0.dll Failed.
   at ESB.Adaptors.Application.Services.ConventionOverConfig.InvokeViaConvention.InvokeObject(String& sTransactionComponent, String& sComponentServer, Envelope& oEnvRq, Envelope& oEnvRs)
   at ESB.Adaptors.Application.Services.ConventionOverConfig.InvokeViaConvention.DoWork()
   at ESB.Adaptors.Application.Services.ConventionOverConfig.InvokeViaConvention.ProcessMsgSync(IEnvelope oEnv)
   at ESB.Core.Pipeline.PipelineExecuter.InvokeObjectCLR(IProcessMsg& oESBIf, Envelope& oEnvRq)"
Source="ESB.Adaptors.Application.Services.ConventionOverConfig"

Why is it still trying to use convention over config?

Here is my pipeline entry:
                    <PipelineMapSection>
                        <PipelineEntry>
                            <ResolveNameEntry>
                                <ContextEntry>
                                    <Context>com.MyDomain.MyService.MyServiceHandler1.0.0.0</Context>
                                    <ResolveName>MyServiceRequestType::http://schemas.datacontract.org/2004/07/MyServiceESBNETAdaptor</ResolveName>
                                    <PipelineID>1</PipelineID>
                                    <ProcessInParallel>0</ProcessInParallel>
                                    <ResponseIsRequestForNextPipelineItem>0</ResponseIsRequestForNextPipelineItem>
                                    <MultiLevelOverrides>
                                        
                                        <RequestQ/>
                                        
                                        <TransactionComponent>MyServiceESBNETAdaptor.MyServiceHandler</TransactionComponent>
                                        
                                        <ComponentServer suffix="no">D:\Projects\Services\MyService\MyServiceESBNETAdaptor\bin\MyServiceESBNETAdaptor.dll</ComponentServer>
                                        
                                        <UseObjectBroker>0</UseObjectBroker>
                                        <ObjectBroker/>
                                        <ObjectBrokerServer/>
                                        
                                        <ValidateInputSchema>0</ValidateInputSchema>
                                        <ValidateOutputSchema>0</ValidateOutputSchema>
                                        <IgnoreInputSchemaValidationErrors/>
                                        <IgnoreOutputSchemaValidationErrors/>
                                        
                                        
                                        <Custom>
                                            <ParamName/>
                                            <ParamValue/>
                                        </Custom>
                                    </MultiLevelOverrides>
                                </ContextEntry>
                            </ResolveNameEntry>
                        </PipelineEntry>

New Post: Runtime Error: Management Console online

minas — Fri, 20 Mar 2009 08:27:22 GMT

Hi Patti,
Thanks for that. The URL was changed after an upgrade. I obviously missed a link.
Please use the links below.

http://servicebus.keystroke.com.au/
http://servicebus.keystroke.com.au/esb/source/management/

Thanks
Cheers
Minas

New Post: Runtime Error: Management Console online

patti — Thu, 19 Mar 2009 19:19:56 GMT

Hi,

bevor installing the esb, i would like to try out the management console under

http://www.esb.net.au/MINAsBlog/tabid/59/EntryID/7/Default.aspx

or

http://60.241.173.62/esb/source/management/default.aspx

specified on .http://keystrokeesbnet.codeplex.com/Wiki/View.aspx?title=About%20ESB.NET&referringTitle=Home.

Page Response is a Server Error in '/' Application.

Is there any chance to fixed it ?

Thx a lot !

regards,
patti

New Post: ESB client error

codenamejohn — Fri, 23 Jan 2009 15:33:41 GMT

Hi Minas,

thnx once again!

Regards,
John

New Post: ESB client error

minas — Thu, 22 Jan 2009 12:25:19 GMT

Hi John,
Yes it does, but not in the traditional queue on client-side sense.
This is by design. (There is also an interface for completely async. processing, but it's not fully implemented).
The current transports wait for an acknowledgement. As such, it's not completely asynchronous from the client's point of view. It actually waits for the server to respond, saying - YES, I've got your message - and from then on, the processing is asynchronous.
The point of this is to be able to guarantee early, that the server is up, has received the request, and will process it.
It also then frees the client of any state management responsibilities for asynchronous processing.
eg. If something like MSMQ was used client-side, then the client applications would have the additional overhead of managing queues etc.
This setup ensures clients can be fairly lightweight in that respect.

When an ESB.NET server is the client, you can achieve a completely async server request by this same mechanism. Just configure a local instance to process the request, and send the request to that local instance. The local instance can then store the message.
Messages are stored in MSMQ.

Options:
1)Client-Server invocation:
In the request payload, set the callSynchronizationType in the header
<header>
    <delivery>
      <from>
        <address>MSMQ:.\private$\esbclientresponseq</address> (where response is sent...can be another ESB.NET instance URL eg. http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc/Default etc.)
        <addressType>MSMQ</addressType>
      </from>
      <callSynchronizationType>1</callSynchronizationType> (1=true)
    </delivery>

2)Server - Pipeline Processing.
If you have a configured service, you can configure multiple handlers. Each of these handlers can be set to run in Parallel to the main Pipeline Request Processing Thread. i.e. Run Async.
   <ResolveNameEntry>
                <ContextEntry>
                  <Context>RunAsync</Context>
                  <ResolveName>BuildCmd2::urn:schemas-biztalk-org:biztalk:BuildCmd2:BuildCmd2</ResolveName>
                  <PipelineID>2</PipelineID>
                  <ProcessInParallel>1</ProcessInParallel> (1=true)
                  <MultiLevelOverrides>
                    <RequestQ>MSMQ:.\private$\ESBRequestQ</RequestQ> (where response is sent...as above...)
                    <TransactionComponent>ESB.Testing.TestTxns.TestTxn1</TransactionComponent>

Limitations:
- There is currently no retry functionality built-in. This is left to WF Orchestrations.
If a transactional Q is setup & error occurs, then the message is available in the Q for re-processing.

HTH

Cheers
Minas

New Post: ESB client error

codenamejohn — Thu, 22 Jan 2009 11:59:56 GMT

Hi Minas, thank you for your answer. I have one more question... Does the ESB.NET support the 'Fire and forget' communication?

New Post: ESB client error

minas — Wed, 21 Jan 2009 19:47:26 GMT

Hi John,
The ConventionOverConfiguration handler looks at some attributes on the handler (after locating the actual assembly), to verify the intended handler is being invoked.
You need to change the attributes of the service handler from something like:

<ESB.Core.Util.Attributes.Service(), ESB.Core.Util.Attributes.Documents(

"WfMessage", "http://www.wfmc.org/standards/docs/Wf-XML")> _
...

to something that matches the payload of your first Document in the Envelope.
In this case, it seems your payload ia another Envelope
"ESBEnvelope::urn:keystroke.com.au.esb.envelope.esbEnvelope.version_1_0_6_0".
so you'd need to change the above attribute to
<ESB.Core.Util.Attributes.Service(), ESB.Core.Util.Attributes.Documents("ESBEnvelope::urn:keystroke.com.au.esb.envelope.esbEnvelope.version_1_0_6_0")> _
in order for it to work.
I suspect this is NOT what you actually intended though. Your client-side code seems to be adding another envelope to the Envelope :).

Check the serialized XML to see what's being sent. This can be done by:
1)Calling Envelope.ToXML()
2)Using a Network sniffer...
3)Looking at the logs using the ESB.NET Management Console once you've submitted the message [probably easiest at this point I guess].

What you generally want to pass in as the Document is some Business-Level meaningful data.

HTH

Cheers
Minas

New Post: ESB client error

codenamejohn — Wed, 21 Jan 2009 15:15:28 GMT

Hi,

I'm having trouble sending requests from sample client application to the ESB.NET test service (everything works fine when using the EMC). I get the following response error every time:

ErrorEntry Code="42" Description="No handler configured for request. Successfully created CLR based component but it did not match the service request parameters, so it was not invoked ==>EsbNetTest01.myServiceHandler<== on Server==>D:\Esb\6.2.1.0_x64\Source\ESB\LobSystems\ns\EsbNetTest01\bin\EsbNetTest01.dll<==Component Server = D:\Esb\6.2.1.0_x64\Source\ESB\LobSystems\ns\EsbNetTest01\bin\EsbNetTest01.dll; Resolve name sought was:ESBEnvelope::urn:keystroke.com.au.esb.envelope.esbEnvelope.version_1_0_6_0; ResolveName from ServiceHandler Attributes was:WfMessage::http://www.wfmc.org/standards/docs/Wf-XML; Service Version sought was:; Service Version from ServiceHandler Attributes was:1.0.0.0; Context:m_sTransactionComponent=EsbNetTest01.myServiceHandler;Context=EsbNetTest01.myServiceHandler; Handler NOT Invoked by Convention Over Configuration Handler." Source="ESB.Adaptors.Application.Services.ConventionOverConfig.InvokeViaConvention:InvokeObject. In Assembly:D:\Esb\6.2.1.0_x64\Source\ESB\Base\Solutions\Main\ApplicationAdaptors\ESB.Adaptors.Application.Services.ConventionOverConfig\bin\ESB.Adaptors.Application.Services.ConventionOverConfig.dll"

Can you point me in the right direction?

Thnx,
John

New Post: Windows XP installation problem

codenamejohn — Tue, 20 Jan 2009 17:33:30 GMT

Hi,

I managed to configure it in the meantime. I renamed the SQL server instance in the Setup_FirstTime script and modified the InstallQueues script (had problems creating queues) by adding "cscript" in front of every entry and substituting "%1" with "Source". After creating virtual directories manually and setting up the ASPNET account permissions, everything was up 'n' flying :)

Regards,
John

New Post: Windows XP installation problem

minas — Mon, 19 Jan 2009 23:54:52 GMT

Hi John,
Have you looked at this thread by any chance?
http://www.codeplex.com/KeystrokeEsbNet/Thread/View.aspx?ThreadId=32489

Let me know if this does not help you out.

Cheers
Minas

New Post: Windows XP installation problem

codenamejohn — Mon, 19 Jan 2009 14:57:49 GMT

Hi,

I have a problem installing the ESB.NET (v6.2.1.0) on the Windows XP machine.
The main issue is that I can't configure the virtual directories despite following the given instructions.

Any suggestions?

Thnx,
John

New Post: Admin login error - ESB.NET 6.2.1.0_x64

minas — Tue, 09 Dec 2008 07:52:13 GMT

Hi Satish,
I suspect you're clicking on the Login page directly. This is a known issue & will be fixed in next release.
In the mean time, just click on any other page, & you'll be directed to the home page, followed by a redirect to the target on successful authentication...

Thanks
Cheers
Minas

New Post: Admin login error - ESB.NET 6.2.1.0_x64

satishkbg — Mon, 08 Dec 2008 16:34:05 GMT

Hi MINAS

I tried your suggestion giving read write permissions to the two identities i created, still same problem,
also i get some error on page, related to URL it is looking for (resource not found)

Regards
Satish