in 2013 its much more simpler! as its a wsp that means you can use powershell the same way that you use powershell for any other wsp!
so you added the wsp, installed the wsp so the final thing would be to enable the feature:
Enable-SPFeature -Identity <Feature> -Url <URL>
the above is run in powershell on the server!
the full guide is:
are you activating the feature at the correct levl (site collection or sub site).
what dependancies are there for this workflow as they must already exists befor deployment. What is your site type? is it a publishing site??
but i have a feeling that your not talking about that but rather the association.
if it needs some accosiation than this might be the solution:
var workflowServiceManager = new WorkflowServicesManager(web);
var workflowSubscriptionService = workflowServiceManager.GetWorkflowSubscriptionService();
//get all workflows associated with the list
var subscriptions = workflowSubscriptionService.EnumerateSubscriptionsByList(listId);
//run all workflows associated with the list
foreach (var workflowSubscription in subscriptions)
var inputParameters = new Dictionary<string, object>();
workflowServiceManager.GetWorkflowInstanceService().StartWorkflowOnListItem(workflowSubscription, itemId, inputParameters);