Workflow Solution Beta Setup Guide

Workflow Solution Beta Setup Guide
Filed under: Workflow Solution Beta

Workflow Solution has gone Beta! Workflow Solution is one of the most exciting new releases at Altiris in years and we're excited for people to start trying it out.

Here's a setup guide if you are installing Workflow solution into your own lab or VM. If you have questions or suggests, please e-mail me (the product manager) with your suggestions.

Thanks and we look forward to your feedback.

The Altiris Product Management Team

Beta Setup Steps

Note: These steps will allow you to install Workflow to the same server as NS but not to publish projects to that server. If you installing workflow to the same server as your NS and need to publish workflows to that server, please follow the directions in the next section.
  1. Install Notification Server 6.0
    1. For instructions on getting NS configured and installed please see the Users Guide or the Knowledge Base
    2. If you are installing Workflow to the same server as Notification Server, and you need to be able to publish workflows to the workflow server, see the next section for installing workflow on the same server as the NS
  2. Install NS SP3 and latest service packs from the solution center
  3. Install Asset Management Suite LIII which will include helpdesk and alert manager and licenses for these solutions
    1. If these solutions aren't licensed, components will not work correctly in some instances
  4. Install ASDK 1.4 (Altiris_SDK_1_4.exe) from the beta site
  5. Install the updated Diagnostics Package (AltirisDiagnostics.6.7.7631.0.msi) from the beta page
  6. Install Altiris Service Layer build 1050 (Altiris_Service_6_0_1050.msi)
  7. Install Workflow Solution build 1058
  8. Install Workflow designer from directory C:\Program Files\Altiris\Workflow\agent

This should get Altiris Workflow Solution installed and running! Good luck and we look forward to your feedback. If you have questions or problems getting it installed, please contact Altiris technical support services.

Setting up Workflow to run on the Same Server as NS

Note: To set up Altiris Workflow Solution to publish directly onto the Notification Server you will need to complete the following steps. Although running the Workflow Server and Notification Server concurrently on the same physical box is supported, for scalability, stability and ease of use it's recommended that Workflow and Notification Server are run on separate servers.

Main Instructions

1. Create a Separate Application Pool

Right-click on the "Application Pools" folder, select "New" and Click "Application Pool."

Click to view.

Name the new app pool "dotNet2"

Click to view.

Click "OK"

2. Create a Separate Website

Open IIS and right-click on the "Web Sites" folder, selected "New" and click "Web Site."

Click to view.

Step through the "Web Site Creation Wizard" that opens.

  • Enter "Workflow Projects" as the site's description. Click "Next"
  • Change the site's port to 8088 (the reason you need to change the port number is because the default website and our new website cannot run on the same port without using host headers to differentiate the two, which is a more advanced configuration and outside of the scope of this document) click "Next"
  • Create a folder on the root called "Workflow Site" and select this folder as the path for the new site's home directory. Click "Next"
  • Select "Read," "Run Scripts," and "Execute" for permissions. Click "Next" and "Finish"

3. Edit New Website to Use New Application Pool

Right-click on your new website (Workflow Projects) and click on "Properties."

Select the "Home Directory" tab.

In the "Application Pool" dropdown list, select the new App Pool we created in the first step.

Click to view.

Select the "ASP.NET" tab.

In the "ASP.NET version" dropdown list, select "2.0.50727"

Click to view.

4. Point Deployment Service to New Website and App Pool

Open "Server Extensions Configurator" (Start > Programs > Altiris > Workflow Designer > Tools > Workflow Designer Server Extensions Configurator)

Click the ellipse next to "Deployment Info"

Click to view.

Change the "Root URL" to http://[MachineName]:8088

Change "IISRoot path" to "IIS://localhost/W3SCV/[NewWebsiteID]/Root"

Click "Ok," "Ok," "Yes," "Ok"

When asked to restart Server Extensions, click "Yes"

Click to view.

Note: see "How to Find a Web Site ID in IIS" section below for help in finding the ID of your new website.

When you have completed all these steps do an IIS reset
(Click Start'Run, Then enter "iisreset" and click "OK")

How to Find a Web Site ID in IIS

In IIS, right-click and click "Properties" on the website you are interested in; "Workflow Projects" in this case.

On the "Web Site" tab, click "Properties".

Click to view.

Notice the "Log file name" at the bottom of the window that opens.

Click to view.

Your Web Site ID is the number that follows the "W3SVC" and precedes the "\"

In this case the Web Site ID is "1724851803"

Troubleshooting

  • After you have completed every change, make sure you run the "iisreset" command from Windows Run.
  • Check to make sure that IIS has not reset the new web site's app pool to the default. For some reason IIS tends to do this from time to time.
  • Save all your changes, close IIS and Workflow Designer, then reboot your computer.
3.92857
Average: 3.9 (14 votes)
AttachmentSize
Workflow Closed Beta Setup Guide.doc1.86 MB

Current Status of the Beta?

jjesse's picture

What is the current status of this beta? I see on beta.altiris.com it now shows as a closed beta. How do you register for this?
Is there still a beta available? I have heard this was brought back to Alpha is that true as well?

Thanks,

JOnathan

workflow beta period

We are in an internal beta period that is currently closed right now. We will be having an open beta period near the end of this month. We would like to get the final issues resolved internally before we open it to a larger crowd.

you can sign up for the open beta at the beta portal at http://beta.altiris.com and wait for an announcement. We're currently anticipating the last week of January but that could be subject to change based on our current testing

Matt Meservey

Thanks

jjesse's picture

I'm already signed up at the beta site, so I'm looking forward to trying it out.

Jonathan

Beta registration / notification

Greetings!

Is there anyway you can notify me when the Beta is available. We recently purchased the Altiris Asset Management Suite III and we need to develop several workflow scenarios (such as approvals for new employees) But we are having considerable difficulty doing so because of the complexity of doing it (yes, we are not programmers by trade) This type of workflow product would help out our implementation process immensely!

Thanks!

Beta no longer closed...

cnpalmer75's picture

Just in case anyone missed it, the beta is no longer closed.

And I must say the dev/product guys on this one are on top of their game for replies to customers etc. Thanks Matt & Andy!

Benjamin Z. Palmer
Architect | Workspace Design | The Hartford | Simsbury, CT 06082

Problems w/ .NET 1.1 and .NET 3.0 not playing nice

jjesse's picture

After installing .NET 3.0 and re-registering .net 1.1, I still get application errors after a restart or when I pause my Altiris VM and then un-pause it.
Anyone else seeing problems?

Jonathan

Syndicate content