Opalis Community Releases

Source code checked in, #69631

Project Collection Service Accounts — Mon, 01 Oct 2012 21:13:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69630

Project Collection Service Accounts — Mon, 01 Oct 2012 21:07:03 GMT

Checked in by server upgrade

Closed Issue: Transform Data [9658]

jfanjoy — Mon, 01 Oct 2012 06:17:10 GMT

hey,

Just wondering what i'm doing wrong here, i want to translate the subnet to a subnetmask like:
24 - 255.255.255.0

So i created the XML file like (see attachment)

But when the subnet is like 24, i get a result what is not as aspected, it looks like the subnet is split into 2 and 4 so it gets all the subnets where a 2 is in the number and all subnets with a 2 in it.

help ?
Comments:

Resolved by user education.

Commented Issue: Transform Data [9658]

Vrakking — Mon, 01 Oct 2012 05:38:46 GMT

Thanks, this was just the kind of help i was looking for, not only did you explaine what i was doing wrong, but you also gave me the solution (and more Method="RegEx") to handle this kind of usage in the future !

Commented Issue: Transform Data [9658]

jfanjoy — Sat, 29 Sep 2012 23:46:46 GMT

The problem is that you are performing multiple replacements against the same data. it does not apply all the replacements as "OR" conditions but rather it applies each replace against the current data.

So if you use a subnet of "24", then what happens is it attempts to process the replacements for 8 through 23 with no matches then when it processes "24", it replaces the string "24" with the string "255.255.255.0". When it then subsequently applies the replace for "25", it replaces each "25" in "255.255.255.0" with "255.255.255.128" so you end up with a string like "255.255.255.1285.255.255.255.1285.255.255.255.1285.0" which then continues to get processed and additional replacements happen with it hits the replace for "28" etc.

My recommendation would be to use the RegEx method so you can clearly control exactly what you want searched for and replaced.

I've modified your XML with a version that should accomplish what you're after. What I did was first apply a "Trim" transform to ensure there are no leading or trailing spaces, then I changed all the replace transforms so that they use regular expression and wrapped each searchstring in ^ and $ which mean start of string and end of string respectively so that when you do a regex search for ^24$ you will only get a match if "24" is the entire string.

Created Issue: Transform Data [9658]

Vrakking — Fri, 28 Sep 2012 08:44:11 GMT

Reviewed: Integration Pack for Data Manipulation (Aug 08, 2012)

Vrakking — Wed, 08 Aug 2012 09:44:19 GMT

Rated 5 Stars (out of 5) - Just one word... WOW :) this was exactly wat i was searching for.

Reviewed: Integration Pack for Data Manipulation (Nov 22, 2011)

fope — Tue, 22 Nov 2011 15:45:42 GMT

Rated 5 Stars (out of 5) - Currently I've only used the Transform Data Object with the XML specification and it works great - Thanks for that! Peter Forster - Microsoft MVP 2002-2011

Updated Wiki: Home

brunosa — Thu, 03 Nov 2011 21:22:19 GMT

[Looking for Orchestrator content? Go to http://orchestrator.codeplex.com]

Opalis Integration Server - Community Releases

This project contains integrations and workflows for Opalis Integration Server that are released by the Microsoft Opalis team. Releasing these integrations via CodePlex allows the team to provide the community with a way to get new integrations more frequently than waiting for new product releases. Watch this site and our TechNet TechCenter for ongoing updates!

New to Opalis? Get Started with these Resources

What's On This Site?

Sample Workflows from the Blog

Community-Developed Integration Packs

Opalis-Related Tools and Utilities

Custom Development Examples

Best Practice Guides & Samples

Opalis Architecture and Workflow Deployment Docs

Downloadable Source Code

Opalis Policy Tree View Example

Other Opalis-Related Projects on CodePlex

General Opalis Extensions:
- Opalis Utilities
- Opalis Scheduled Tasks Integration Pack
Opalis Extensions for System Center products:
Opalis Extensions for other Microsoft products / technologies:
Opalis Extensions for 3rd-Party products:
- VMWare VSphere IP
- Virsto Integration Pack

Updated Wiki: Home

brunosa — Thu, 03 Nov 2011 21:21:21 GMT

[Looking for Orchestrator content? Go to http:/orchestrator.codeplex.com]

Opalis Integration Server - Community Releases

New to Opalis? Get Started with these Resources

What's On This Site?

Sample Workflows from the Blog

Community-Developed Integration Packs

Opalis-Related Tools and Utilities

Custom Development Examples

Best Practice Guides & Samples

Opalis Architecture and Workflow Deployment Docs

Downloadable Source Code

Opalis Policy Tree View Example

Other Opalis-Related Projects on CodePlex

General Opalis Extensions:
- Opalis Utilities
- Opalis Scheduled Tasks Integration Pack
Opalis Extensions for System Center products:
Opalis Extensions for other Microsoft products / technologies:
Opalis Extensions for 3rd-Party products:
- VMWare VSphere IP
- Virsto Integration Pack

Released: OIS - SCOM Extensibility Kit 2.0 (août 17, 2010)

Thu, 03 Nov 2011 20:21:16 GMT

Opalis Integration Server & System Center Operations Manager Extensibility Kit 2.0

The Opalis Integration Server (OIS) – System Center Operations Manager (SCOM) Extensibility Kit 2.0 includes examples of how to extend SCOM using both the SCOM and OIS SDKs. The C# code and compiled DLL included here offer two OIS objects which can be used to automatically create or delete notification subscriptions based on an existing Channel as well as work against existing Pending Agent Installs in the SCOM database.

Included in this Extensibility Kit:

Opalis Ready DLL:
Can be used with the “Invoke .NET” object included in the Integration Pack for “Opalis Quick Integration Kit for Microsoft .NET”
- OpalisSCOMExtensibility.dll
- NOTE: This DLL is dependent on some other resources, see System Requirements.

C# Source Code:
Example C# Source Code illustrating the combination of the SCOM and OIS SDKs.
- SCOM_NoteSubcriptionCreate.cs
- SCOM_NoteSubcriptionDelete.cs
- SCOM_AgentInfoAdapter.cs
- SCOM_ApprovePendingAgentInstall.cs
- SCOM_ListPendingAgentInstalls.cs
- NOTE: These C# files are dependent on some other resources, see System Requirements.

This Extensibility Kit (DLL to be used with the Opalis “Invoke .NET” object) adds the following object capability to Opalis Integration Server:

Create SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionCreate)
Delete SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionDelete)
List Pending Agent Installs (SCOM.SCOMSDK.SCOMListPendingAgentInstalls)
Approve Pending Agent Installs (SCOM.SCOMSDK.SCOMApprovePendingAgentInstall)

This DLL (and appropriate dependencies) can be rolled up into an Opalis Integration Pack (not included here) by using the QIK Wizard.

Please Refer to the OIS-SCOM Extensibility Kit 2.0 - User Guide for more information on System Requirements, Installation, Configuraiton and Usage.

Updated Release: OIS - SCOM Extensibility Kit 2.0 (Aug 17, 2010)

charlesjoy — Thu, 03 Nov 2011 20:21:16 GMT

Opalis Integration Server & System Center Operations Manager Extensibility Kit 2.0

Opalis Ready DLL:
Can be used with the “Invoke .NET” object included in the Integration Pack for “Opalis Quick Integration Kit for Microsoft .NET”
- OpalisSCOMExtensibility.dll
- NOTE: This DLL is dependent on some other resources, see System Requirements.

C# Source Code:
Example C# Source Code illustrating the combination of the SCOM and OIS SDKs.
- SCOM_NoteSubcriptionCreate.cs
- SCOM_NoteSubcriptionDelete.cs
- SCOM_AgentInfoAdapter.cs
- SCOM_ApprovePendingAgentInstall.cs
- SCOM_ListPendingAgentInstalls.cs
- NOTE: These C# files are dependent on some other resources, see System Requirements.

This Extensibility Kit (DLL to be used with the Opalis “Invoke .NET” object) adds the following object capability to Opalis Integration Server:

Create SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionCreate)
Delete SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionDelete)
List Pending Agent Installs (SCOM.SCOMSDK.SCOMListPendingAgentInstalls)
Approve Pending Agent Installs (SCOM.SCOMSDK.SCOMApprovePendingAgentInstall)

Updated Release: OIS-SCOM Extensibility Kit 2.0 (Aug 17, 2010)

charlesjoy — Thu, 03 Nov 2011 20:20:50 GMT

Opalis Integration Server & System Center Operations Manager Extensibility Kit 2.0

Opalis Ready DLL:
Can be used with the “Invoke .NET” object included in the Integration Pack for “Opalis Quick Integration Kit for Microsoft .NET”
- OpalisSCOMExtensibility.dll
- NOTE: This DLL is dependent on some other resources, see System Requirements.

C# Source Code:
Example C# Source Code illustrating the combination of the SCOM and OIS SDKs.
- SCOM_NoteSubcriptionCreate.cs
- SCOM_NoteSubcriptionDelete.cs
- SCOM_AgentInfoAdapter.cs
- SCOM_ApprovePendingAgentInstall.cs
- SCOM_ListPendingAgentInstalls.cs
- NOTE: These C# files are dependent on some other resources, see System Requirements.

This Extensibility Kit (DLL to be used with the Opalis “Invoke .NET” object) adds the following object capability to Opalis Integration Server:

Create SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionCreate)
Delete SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionDelete)
List Pending Agent Installs (SCOM.SCOMSDK.SCOMListPendingAgentInstalls)
Approve Pending Agent Installs (SCOM.SCOMSDK.SCOMApprovePendingAgentInstall)

Updated Release: OIS - Data Extraction and Reporting Kit 1.0 (Dec 17, 2010)

charlesjoy — Thu, 03 Nov 2011 20:19:55 GMT

Opalis Data Extraction and Reporting Kit

The Opalis Data Extraction and Reporting Kit is a sanitized* and packaged “kit” of examples you can use as a guide for your own Opalis powered Reporting use case. This example content is based on and directly related to the following blog post: http://blogs.technet.com/b/charlesjoy/archive/2010/12/16/8-minute-demo-scdemo-reporting-powered-by-opalis.aspx

Included in this Data Extraction and Reporting Kit:

Download File: OpalisDataExtractionandReportingKit.zip

Example Sanitized Workflows
- RPTDBWorkflowTemplates.ois_export
Example Hyper-V PowerShell Script
- The PowerShell Management Library for Hyper-V is used extensively within the example. (http://pshyperv.codeplex.com/)
- HyperVScan.ps1
Example OS PowerShell Script
- VMHostOSAudit.ps1
Example OS CLI Commands
- CLICommands.txt
Example SQL Database Table and View Structure
- SQL Scripts for the DROP/CREATE and SELECT Statements
- 16 Individual .sql DROP/CREATE files
Example C# Script for Parsing Input
- ParseGroupMembers.cs
Example Sanitized Excel 2010 Report
- RPTDBUsageReport.xlsx

*SCDEMO has been changed to RPTDB, all production names and references have been removed, all non-reporting workflows have been removed, etc.

Released: OIS - Data Extraction and Reporting Kit 1.0 (déc. 17, 2010)

Thu, 03 Nov 2011 20:19:55 GMT

Opalis Data Extraction and Reporting Kit

Example Sanitized Workflows
- RPTDBWorkflowTemplates.ois_export
Example Hyper-V PowerShell Script
- The PowerShell Management Library for Hyper-V is used extensively within the example. (http://pshyperv.codeplex.com/)
- HyperVScan.ps1
Example OS PowerShell Script
- VMHostOSAudit.ps1
Example OS CLI Commands
- CLICommands.txt
Example SQL Database Table and View Structure
- SQL Scripts for the DROP/CREATE and SELECT Statements
- 16 Individual .sql DROP/CREATE files
Example C# Script for Parsing Input
- ParseGroupMembers.cs
Example Sanitized Excel 2010 Report
- RPTDBUsageReport.xlsx

*SCDEMO has been changed to RPTDB, all production names and references have been removed, all non-reporting workflows have been removed, etc.

Updated Release: Opalis Data Extraction and Reporting Kit 1.0 (Dec 17, 2010)

charlesjoy — Thu, 03 Nov 2011 20:19:10 GMT

Opalis Data Extraction and Reporting Kit

Example Sanitized Workflows
- RPTDBWorkflowTemplates.ois_export
Example Hyper-V PowerShell Script
- The PowerShell Management Library for Hyper-V is used extensively within the example. (http://pshyperv.codeplex.com/)
- HyperVScan.ps1
Example OS PowerShell Script
- VMHostOSAudit.ps1
Example OS CLI Commands
- CLICommands.txt
Example SQL Database Table and View Structure
- SQL Scripts for the DROP/CREATE and SELECT Statements
- 16 Individual .sql DROP/CREATE files
Example C# Script for Parsing Input
- ParseGroupMembers.cs
Example Sanitized Excel 2010 Report
- RPTDBUsageReport.xlsx

*SCDEMO has been changed to RPTDB, all production names and references have been removed, all non-reporting workflows have been removed, etc.

Updated Release: OIS - iSCSI Automation Kit 1.0 (Apr 25, 2011)

charlesjoy — Thu, 03 Nov 2011 20:18:19 GMT

OIS - iSCSI Automation Kit v1.0

The OIS - iSCSI Automation Kit v1.0 includes policy examples of how to automate/orchestrate Windows 2008 R2 NIC settings as well as the iSCSI Initiator configuration using OIS and the available CLIs.

Included in this iSCSI Automation Kit are 12 policies:

Setup
- Maintenance | SAN | 0.0 Create SQL Tables for External Data Persistence Store

Prep SCDEMO Hosts
- Maintenance | SAN | 1.0 SCDEMO Hyper-V VHD Scan for Running VMs on SAN
- Maintenance | SAN | 2.0 Stop VMs on SAN

Disable iSCSI Resources
- Maintenance | SAN | 3.0 Disable iSCSI NIC
- Maintenance | SAN | 4.0 Remove Favorite Target from iSCSI Initiator
- Maintenance | SAN | 5.0 Logout of iSCSI Initiator Target Session
- Maintenance | SAN | 6.0 Remove iSCSI Target Portal and Refresh

Enable iSCSI Resources
- Maintenance | SAN | 7.0 Add IP Address to iSCSI NIC
- Maintenance | SAN | 7.1 Enable iSCSI NIC
- Maintenance | SAN | 7.2 Delete Old iSCSI IP Address
- Maintenance | SAN | 8.0 Add Target Portal to iSCSI Initiator
- Maintenance | SAN | 9.0 Login to iSCSI Initiator Target and Add Fav Target

Please Refer to the TechNet Blog Post (http://blogs.technet.com/b/charlesjoy/archive/2011/04/25/ois-iscsi-initiator-automation.aspx) for more information on this use case example.

Released: OIS - iSCSI Automation Kit 1.0 (avr. 25, 2011)

Thu, 03 Nov 2011 20:18:19 GMT

OIS - iSCSI Automation Kit v1.0

Setup
- Maintenance | SAN | 0.0 Create SQL Tables for External Data Persistence Store

Prep SCDEMO Hosts
- Maintenance | SAN | 1.0 SCDEMO Hyper-V VHD Scan for Running VMs on SAN
- Maintenance | SAN | 2.0 Stop VMs on SAN

Disable iSCSI Resources
- Maintenance | SAN | 3.0 Disable iSCSI NIC
- Maintenance | SAN | 4.0 Remove Favorite Target from iSCSI Initiator
- Maintenance | SAN | 5.0 Logout of iSCSI Initiator Target Session
- Maintenance | SAN | 6.0 Remove iSCSI Target Portal and Refresh

Enable iSCSI Resources
- Maintenance | SAN | 7.0 Add IP Address to iSCSI NIC
- Maintenance | SAN | 7.1 Enable iSCSI NIC
- Maintenance | SAN | 7.2 Delete Old iSCSI IP Address
- Maintenance | SAN | 8.0 Add Target Portal to iSCSI Initiator
- Maintenance | SAN | 9.0 Login to iSCSI Initiator Target and Add Fav Target

Please Refer to the TechNet Blog Post (http://blogs.technet.com/b/charlesjoy/archive/2011/04/25/ois-iscsi-initiator-automation.aspx) for more information on this use case example.

Updated Release: OIS - Orchestrated Cloud App Deployment Kit 1.0 (Jun 07, 2011)

charlesjoy — Thu, 03 Nov 2011 20:17:37 GMT

OIS - Orchestrated Cloud App Deployment Kit

The OIS - Orchestrated Cloud App Deployment Kit includes policy examples of how to automate/orchestrate Windows Azure Application Deployment using OIS, Service Manager and the available PowerShell Cmdlets.

Included in this Orchestrated Cloud App Deployment Kit are 7 example OIS Policies and 6 example PowerShell PS1 files:

Example OIS Policies
- Azure Deployment | 0.0 Initiate Azure Deployment
- Azure Deployment | 1.0 New Deploy Package
- Azure Deployment | 2.0 Update Deploy Status
- Azure Deployment | 3.0 Update Deploy Package
- Azure Deployment | 4.0 Remove Deploy Package
- Azure Deployment | 99.0 Create Change Request
- Azure Deployment | 99.1 Copy Files
- NOTE: The Integration Pack for System Center Service Manager is required for these example OIS Policies

Example PowerShell PS1 Files
- deployAzurePackage.ps1
- getAzureDeploymentLabel.ps1
- getAzureDeploymentURL.ps1
- removeAzureDeployment.ps1
- setAzureDeploymentStatus.ps1
- updateAzurePackageDeployment.ps1

Please Refer to the TechNet Blog Post (http://blogs.technet.com/b/charlesjoy/archive/2011/06/08/8-minute-demo-orchestrated-cloud-application-deployment.aspx) for more information on this use case example.

Released: OIS - Orchestrated Cloud App Deployment Kit 1.0 (juin 07, 2011)

Thu, 03 Nov 2011 20:17:37 GMT

OIS - Orchestrated Cloud App Deployment Kit

Example OIS Policies
- Azure Deployment | 0.0 Initiate Azure Deployment
- Azure Deployment | 1.0 New Deploy Package
- Azure Deployment | 2.0 Update Deploy Status
- Azure Deployment | 3.0 Update Deploy Package
- Azure Deployment | 4.0 Remove Deploy Package
- Azure Deployment | 99.0 Create Change Request
- Azure Deployment | 99.1 Copy Files
- NOTE: The Integration Pack for System Center Service Manager is required for these example OIS Policies

Example PowerShell PS1 Files
- deployAzurePackage.ps1
- getAzureDeploymentLabel.ps1
- getAzureDeploymentURL.ps1
- removeAzureDeployment.ps1
- setAzureDeploymentStatus.ps1
- updateAzurePackageDeployment.ps1