Workflow Soluiton

How can I verify that my workflows are using SQL Based State Data?  It seems some of my workflow that were moved from my old workflow server are using file based instead of SQL based.

Easiest way to check:

Open Workflow Explorer. Go to the SymQ Configuration tab. Check the local.workflow- queue (2nd from the bottom) and see what this alias exchange is delivering to.

If its local.workflowsqlexchange-, it's SQL based. If it's file based, it'll be delivering to some file exchange (can't think of the name off the top of my head - LocalFileStorage-, I think).

Note that workflow persistence is server-based, not on a per workflow basis. If your workflow server persistence is SQL based, all of them use SQL to persist their data.

Also, it's advised not to change these exchanges unless you know what you're doing. Flipping from SQL to file persistence will likely result in lost data unless you take precautions.

I don't see aything under SymQ configuration tab called local.workflow.  All I see is SymQ_Local_Defaults, SymQ_Core, Process_manager, Workflow_Core.

It should be under SymQ_Local_Defaults. Click that on the left, and it should appear toward the bottom of the window on the right.

reecardo,

I have a new server that is set to use File-based (LogicBase.Core.Messaging.AliasExchangeImpl). how do I set it to be SQL-based?

Kindest regards,

QuietLeni

Hello Quieleni,

If I'm reading reecaro's erlier post correctly LogicBase.Core.Messaging.AliasExchangeImpl is SQL-based.

No, an alias exchange is neither SQL-based nor file based; it's basically an exchange type that acts as an alias for another exchange... that other exchange could be SQL-based, could be file based.

reecardo,

OK, I just checked again on the server and I see:

lme://127.0.0.1/LBME.Workflow-

in the Delivery To Queue.

How do i set it to SQL instead? I was looking in SymWise and I found this for 6.5:

http://www.symantec.com/business/support/index?page=content&id=HOWTO9601

However, I cannot find the equivalent dbtool.exe on the 7.1 SP2 server!

Kindest regards,

QuietLeni

Depending on what version of workflow you have, you could try re-running the installer and specify SQL instead of File on the Persistence page of the installer.

To do it manually requires a little bit of work... find the local.workflow- exchange (described above) and try to change the Deliver To Queue: to local.workflowsqlexchange- if it exists.

That's the easy part. The problem then becomes if you have various messages in file form that need to be dumped into the SQL database. There exists no easy way to do this, though I've heard of it being done.

DbTool was removed in 7.0 I believe... that article wouldn't apply to anything past that if it references dbtool.

Just verifying... are you looking at the local.workflow- queue? That's the one that should be redirected from a file to a sql queue. You shouldn't have to worry about the LBME.Workflow- queue. Also, everything I'm telling you is for 7.1 SP2, inside Symantec Explorer (the evolved Confiuration and Logging Tool of the 7.0 days)

reecardo,

Yes, I had to re-run the installer to set the Persistence to SQL and now it is set to use SQL Server. The SQL Server has the Message and MessageLog(?) tables in it now. I think that the Admin who installed it originally had clicked the back button after they had gone through the screens and this resets back to File, not SQL.

As to whether the other Workflows have been broken, the only one on this machine is the Worfkflow Approval(?) one and I do not think that we are using that.

Thanks for the help. Perhaps this will help someone else.

Regards,

QuietLeni