BLToolkit - Current readiness for Azure - bltoolkit

Does anybody know if BLToolkit has been tested and certified for use with Azure Sql and if it supports the dropped connection retry functionality? And if not are there any plans to get it tested and passed?

At the time of writing, there is nothing official on the BL Toolkit website, and no issues listed in their issue tracker for Azure.
There are a few other requests (e.g. here and here) that are requesting the same details. At the moment they are unanswered but you could add your weight to them.
Based on this evidence from the official sources I would say that the Toolkit is not Tested or Certified specifically for Azure use.
With the exception of the transient nature of Azure which may require handling of database reconnections, there doesn't seem to be anything obvious that would prevent you from using the Toolkit however.
I would recommend you raise an issue with the developers regarding Azure Testing and Certification while performing a proof of concept test on Azure to determine how to best handle reconnections on Azure for your specific application.
There is recent activity on the project, so I'd be quite hopeful of a response.

I wrote Azure Sql Data Provider for BLToolkit. You can find its sources on github.
Also it's available over NuGet. Please, see how to install and configure it here.

Related

Websphere Migration from was7 to was9

Planning to Migrate the Websphere from 7.0 to 9 and 8.5 to 9.
Can anyone help me getting the detailed Process
Migration here is "In place". (Migration will be done on the same servers, where the old Installation are in)
if at all any migration tools need to be used, please provide the clear info on them.
any documental references, or any video references for the questioner is appreciated.
OS used : RHEL
CUrrent version: WAS 7x and 8.5
Migrating to : WAS 9.0
It sounds like you're in the very beginning stages of doing this migration. Therefore, I highly recommend you take some time to plan this out, especially to figure out the exact steps you'll be taking and how you'll handle something going wrong. For WebSphere, there is a collection of documents from IBM that discuss planning and executing the upgrade. Look around there for documentation on the tools and step by step guides for different kinds of topologies. The step by step guide for an in place migration of a cell is here.
You should make sure to take good backups before you start the process so you can restore back to before the migration if you need to.
In addition to doing the upgrade, an important part is to also make sure your applications are going to work on the new version if you haven't already. IBM provides this tool to scan applications and identify potential issues that developers will have to fix. There is documentation for the tool at that link as well.
If you are in the planning phase, I'd strongly suggest you to consider migrating to WebSphere Liberty instead of traditional WAS v9. All these migration tools (toolkit for binaries, Eclipse migration toolkit) support both migration scenarios.
Choosing Liberty might be a bit more work at the beginning, but you will gain more deployment flexibility and speed up future development. Liberty is also much better fitted for any cloud/containers environments, as it is much more lightweight, so in the future, if you would like to move to containers, it would be much easier.
Check this tutorial Migrate traditional WebSphere apps to WebSphere Liberty on IBM Cloud Private by using Kubernetes, although it shows the steps to migrate to Liberty on ICP, beginning is the same - analyzing of the application whether they are fit for Liberty and migrating. If you don't have access to IBM Cloud or ICP, you can use stand alone version of the Transformation Advisor that was released recently - IBM Cloud Transformation Advisor.
Having said all that, some apps include old or proprietary traditional WebSphere APIs and in that case it may be easier and cheaper to temporary migrate them to WAS v9, and modernize in the future.

Deepstreamhub problems with creating apps

I've been unable to create new apps (or signup for a new ones) on deepstreamhub.com
There are no responses on their slack channel and no responses from support.
Are anyone out there running serious production systems of deepstreamhub (the hosted solution) or deepstream.io (the open source server)
We are trying to implement it but runs in the lots of little problems like this.
The software is a fantastic concept, and it works great (most of the time).
The open source server (deepstream.io) for self hosting is very important to our usage. But if the service for signup is this non-existent, it makes me worry.
Deyan, thanks for your answer and the continuous presence of ably around our ecosystem. As hinted at deepstreamHub - the hosted platform - will be discontinued to allow us to fully focus on the enterprise versions as well as open source - with deepstream v4 on the very near horizon.

How to avoid deployment of apps and adapters twice on Mobilefirst?

We have developed multiple apps and adapters as part of our project
We have written little ant scripts to deploy the 'apps' and 'adapters',
Prior executing 'ant tasks' we want to know whether the apps and adapters were already deployed or not
Can I use the tables 'PROJECT_ADAPTERS' and 'PROJECT_APPLICATIONS' to avoid the duplicate deployment? (or) What will happen if try to deploy same 'apps' and 'adapters' twice by mistake ?
You should treat the worklight server as a black-box, although in purely technical terms you can investigate the database and deduce information in doing so you are not using a formal API and hence anything you do is unsupported and may become invalid in future product releases.
However there are published ant tasks for retrieving the list of deployed applications and adapters, so in principle you can use those. However I query the wisdom of doing so. My primary concern is that I don't see how knowing that some version of your artefact is deployed is significant. Suppose you have changed the source, don't you want to deploy anyway?
The ant tasks are documented in the InfoCentre. Search for the topic Administering MobileFirst Applications through ant. Here's a link that works today.
As Idan has indicated there is some degree of cleverness in the build tools to avoid redundant deployment. I suggest you just use the tools as they stand rather than try to circumvent them via back-door approaches.
Nothing bad will happen by re-deploying an adapter or application.
In fact, if the checksum is identical between the already-deployed .wlapp/.adapter and the to-be deployed .wlapp/.adapter, it may not get deployed at all. And if they do get deployed, twice, and it's exactly the same apps and adapters (no code changes), then they'll just be deployed again (they will not be duplicated).

Connecting Ektron with third party enterprise systems

I am working in ektron 8.6.
I am trying to connect a third party enterprise systems to ektron.
DxH has got a pre-built marketing automation connector,which is Marketo.
My third party enterprise connector is also a marketing automation system.
I am following the developer webinar to get this done.
Now,my question is eventhough i made establishing connection to the third party system by means of ConextBus API,i need to make some changes in the workarea files for implementing certain functionalities.
So is it necessary to have the connection established via DxH?
What is the significance of this compared to handling all these functionalities from the ektron site?
Can anyone provide me some insight on this?
If you're asking "why use DxH?" the main answer is its tight integration with Ektron. You can continue using your marketing automation system and it will share relevant data with Ektron. If you are instead looking to perform a wholesale migration away from a particular system, you can certainly do a one-time import of data into Ektron using the APIs. The difference there is that you would be moving away from the 3rd party system, whereas the DxH and its ContextBus allows both systems to work together.
You mentioned a webinar that you are following, so you may have already seen this, but there's a good webinar on the DxH here: http://www.ektron.com/Webinars/Details/Digital-Experience-Hub---Developer-Webinar/

Is there any reason not to host a software repository with a standard web hosting service?

I have webspace and I was thinking of setting up a git repository on it.
If I am developing software and I want to host a repository (CVS, SVN, git, etc) online, is there any reason not to use a standard web hosting provider (GoDaddy, etc) to do this?
I'm thinking in terms of security, reliability, etc.
One reason for not using a standard-company is that usually shell-access is needed to setup a Version Control System (VCS). Many providers don't give shell access on normal webspaces.
When you are developing open-source software I'd recommend hosting at SourceForge, github, Google Code or similar providers, as your code is public there, you will get an issue tracker and several other tools that may help you. On github for example adding more developers to your project is very easy.
When you are developing closed-source software you still can use github, this gives you the same advantages as mentioned above, but of course it costs you a few bucks a month. Open-Source projects are free.
So while there is no real reason to not use standard hosting providers there are good reasons to use a company dedicated on hosting code.
As you asked especially for security: github (I use it as an example, as I host my code there as well) gives you a full list of information of what they do to ensure your code is safe.