Azuqua was a tool that helped users integrate their SaaS applications and build custom automations. It was acquired by Okta in late 2019, and is now part of Okta Workflows. Okta Workflows leverages Azuqua’s workflow orchestration engine and application integrations to automate complex identity-centric processes such as user onboarding and offboarding. The product is available as part of the Okta Lifecycle Management…
N/A
OpenText MBPM
Score 7.2 out of 10
N/A
OpenText acquired BPM solution Metastorm in 2011, and has rebranded the product as OpenText MBPM. It is an alternative BPM solution to OpenText's primary BPM offering called OpenText Cordys Business Process Management.
N/A
SSIS
Score 7.6 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
Okta Workflows
OpenText MBPM
SQL Server Integration Services (SSIS)
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Okta Workflows
OpenText MBPM
SSIS
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Okta Workflows
OpenText MBPM
SQL Server Integration Services (SSIS)
Features
Okta Workflows
OpenText MBPM
SQL Server Integration Services (SSIS)
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
7.0
3 Ratings
11% below category average
SQL Server Integration Services (SSIS)
-
Ratings
Dashboards
00 Ratings
7.93 Ratings
00 Ratings
Standard reports
00 Ratings
9.02 Ratings
00 Ratings
Custom reports
00 Ratings
4.03 Ratings
00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
7.3
3 Ratings
13% below category average
SQL Server Integration Services (SSIS)
-
Ratings
Process designer
00 Ratings
8.13 Ratings
00 Ratings
Process simulation
00 Ratings
7.13 Ratings
00 Ratings
Business rules engine
00 Ratings
9.02 Ratings
00 Ratings
SOA support
00 Ratings
6.02 Ratings
00 Ratings
Process player
00 Ratings
7.02 Ratings
00 Ratings
Support for modeling languages
00 Ratings
8.02 Ratings
00 Ratings
Form builder
00 Ratings
6.93 Ratings
00 Ratings
Model execution
00 Ratings
6.13 Ratings
00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
7.6
3 Ratings
9% below category average
SQL Server Integration Services (SSIS)
-
Ratings
Social collaboration tools
00 Ratings
7.63 Ratings
00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
6.0
2 Ratings
30% below category average
SQL Server Integration Services (SSIS)
-
Ratings
Content management
00 Ratings
6.02 Ratings
00 Ratings
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
-
Ratings
SQL Server Integration Services (SSIS)
7.0
56 Ratings
16% below category average
Connect to traditional data sources
00 Ratings
00 Ratings
9.056 Ratings
Connecto to Big Data and NoSQL
00 Ratings
00 Ratings
5.043 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
-
Ratings
SQL Server Integration Services (SSIS)
6.8
56 Ratings
17% below category average
Simple transformations
00 Ratings
00 Ratings
9.056 Ratings
Complex transformations
00 Ratings
00 Ratings
4.755 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
-
Ratings
SQL Server Integration Services (SSIS)
7.5
54 Ratings
4% below category average
Data model creation
00 Ratings
00 Ratings
9.028 Ratings
Metadata management
00 Ratings
00 Ratings
6.035 Ratings
Business rules and workflow
00 Ratings
00 Ratings
7.045 Ratings
Collaboration
00 Ratings
00 Ratings
9.040 Ratings
Testing and debugging
00 Ratings
00 Ratings
6.351 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
Azuqua is well suited to connect data based systems or to add an extra level of automation to Smartsheet without requiring the control center. It is also well suited for people who don't have in depth understandings of programming. The UI is mostly visual with click and drag systems instead of requiring manually entered variables.
Metastorm is well-suited for scenarios in which internal stress testing an application is needed in a hurry before showcasing it to potential customers. It supports different views of the process from Swimlane perspective, so different methodologies can be handled. It is an Enterprise level tool and handles both small and large projects quite well, although smaller companies may be stressed out by the amount of time it takes to properly maintain the application.
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
The concept of reduced code to simplify use by less technical teams lowers the barriers to integration and allows teams to collaborate with ideas and concepts much easier
The ability to review simply any error cases simplifies the old approaches of debugging and reviewing large and complex logs
While not strictly part of the platform the support team's efforts to assist, to help clarify issues and then (where necessary) to resolve bugs was a large benefit and a key driver to extend the platform's footprint.
The lack of connection/card documentation. Every card does have a section with details, but they are sometimes lacking.
The help center and community also need some structuring work. Every single connection/app should have a section with detailed documentation regarding its triggers and actions.
The FLO history section needs to be more refined. It sometimes does not load and choosing the date doesn't actually show execution results from that particular day.
The Metastorm process engine is based on an older version of .NET. Updating to a newer version would resolve several known issues with .NET email functionality.
Metastorm builds web pages at run time. While the UI presented to the end user is fine, the Document Object Model is convoluted and subject to change with new releases. Providing a more simplified DOM or at very least a custom function to replace document.getElementById() would make client-side scripting a much more powerful tool.
One function that I've seen Metastorm competitors do well, is email wizards. Having a WYSIWYG email editor would be really nice.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
The system is working as it should, keeping our programs safe from outside hackers. Helping us keep our passwords safe, convenient and already ready to get us logged into the program securely and quickly. Verification that only authorized users are able to access our company's programs. Okta Workflows (Azuqua) is a very good system that has helped our company greatly.
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
I had to use the Automate tool for funneling image assets in bulk (tens of thousands) from FTPs into various destinations on an eCommerce platform. The user interface was quite harsh in comparison to Azuqua. Far more text/code line driven.
We found that OpenText MBPM held its own quite well against IBM BPM. We ended up choosing OpenText MBPM due to the analytics, complex routing, and the ease of SOA service integration. Furthermore, the ability to quickly develop simple User interfaces make this tool a daily component of our most-used toolbox components.
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.