Small query generally. If one got Mule EE with Cloudhub edition licence. MMC will come by default included in it or required to get the separate licencing for that.
If that is the case, what would be the deployment. Are we need to deploy the application separately both in cloudhub and also in MMC.
Else MMC can be used only with standalone servers?.
Correct, MMC is only used with standalone servers. When using Cloudhub, you are able to manage applications via the Cloudhub Console (with no extra license) which allows you to perform tasks similar to those available in MMC. The features available are not identical to MMC's, they are intended only for Cloud applications.
Related
I want to get the deployment method using Powershell for Self-Hosted Integration Runtime.
The requirement is to track whether the SHIR is installed using "Powershell" commands Or its done through the Azure Portal by a human user by manual steps.
Is there any Flag in Azure which indicates the method of the resource deployment? i.e. if its a PowerShell/ARM template/Portal deployment?
Self-Hosted Integration runtime is a service installed on a windows operating machine (the only OS supported now) either on cloud(VM) or on-prem. Closest you can get to its details is under Applications and Services Logs on system Event Viewer, here you can Filter Logs for timestamp between Start and End of your ADF Pipeline.
Additionally, if you feel this is not helpful, you can share your Feedback so the product team can look into this idea. ✌
In Latest Mule version I have noticed they are using the terminology as iPaaS for cloudHub. Does any of you know what are the changes in these two terms?
There isn't any change in the premise of what Cloudhub is. It has always been iPaaS as your using it to publish your application for integration. IaaS will be the AWS and supporting items under the hood, Cloudhub is the iPaaS that your application runs on. This is just a nomenclature change to be more precise.
My team is working on the migration of a hybrid app from Tibco Silver Mobile(TSM) platform to IBM MobileFirst Platform.
I have a JAX-RS webservice developed using Weblogic IDE which is currently hosted on TSM server. This webservice does a security check for all the incoming back-end requests and pass the request to the back-end if it is from a valid source.
When the app will be migrated from TSM to MobileFirst platform the TSM server will be moved out of the scene. I am looking for some alternate options for hosting this JAX-RS webservice. I don't want to make any changes to the webservice since it is a tested and proven code used in the TSM based solution.
I understand from the IBM MobileFirst Platform 7.0 documentation that JAX-RS support is now available on the MobileFirst Server and JAX-RS specification based Java adapters can be developed and deployed to the server.
Can I deploy the above mentioned webservice .WAR file as such to MobileFirst Server, without making any customizations?
If yes, what is the procedure for deploying the webservice (.WAR) to MobileFirst Server?
If no, what are the alternate options that can be considered?
As indicated in the comments above:
MFP Server is actually a Java EE application deployed to a supported Java EE application server, WebSphere Liberty or full WebSphere ND being the normal options, though TomCat is also supported.
In principle your own JAX/RS WAR file can be deployed to these same servers, the details will depend upon exactly what Java EE features you exploit and you will need to understand those Java EE servers' administration model. MFP itself is not affected by this, and you need no MFP knowledge to do it. You just need to understand the chosen Java EE server. Personally I would start with WebSphere Liberty.
A further question would be whether it is better to isolate your JAX/RS and Mobile First servers into their own Java EE server instances. It can be easier to manage and scale if you keep things separate, but technically there should be no interference if you do co-locate them. It is pretty trivial to spin up a dedicated Liberty server.
A more interesting question is whether there is value in actually exploiting the MFP Adapter capability to create JAX/RS services. In effect it's your familiar JAX/RS programming model but packaged slightly differently, deployed as a MFP adapter, and with the option explicitly to exploit the MFP security model and easily call other MFP adapters.
Personally, if I were coming to a project with no existing JAX/RS services and have commited to MFP and its security model then I would do my JAX/RS in the MFP Adapters.
When you access to worklight console you have the list of runtime environments deployed (.war projects). Then you can enter to each environment and operate with the applications, adapters, analytics, etc.
Reading the documentation I found there are several roles you can configure to operate with the worklight console.
The question is if it is possible to configure those roles per runtime environment, or any other way to define different group of users that will have permission to access to each runtime environment.
If it is not, would it be supported to install more than one Worklight console in the same WAS server? This way we could define different roles for each console.
Concerning the question about deploying several Worklight consoles in the same WAS server, the response is yes. You have to use of course different context roots for the different Worklight consoles/Worklight admin services and specify a different value for the JNDI property ibm.worklight.admin.environmentid. The Worklight runtime must have the same ibm.worklight.admin.environmentid that the one used for the console that handles this runtime.
There is no differentiation between runtimes (in either Worklight Foundation 6.2 or MobileFirst Platform Foundation 6.3).
After logging-in (to the Management console), the role the user is applied with will be the one used for any interaction with any runtime.
You may submit an enhancement request: https://developer.ibm.com/mobilefirstplatform/help/
When using the WebSphere Analytics Platform, can multiple Worklight 6.0 application WAR installations (i.e. consoles) point to a single instance of the Analytics piece? Or, do you have to install a separate Analytics instance for each WAR?
Yes, you can have more than one WAR pointing to the same IWAP (IBM WebSphere Analytics Platform) instance; you also can point to different IWAP instances if you want to. When you search in IWAP, it will display from which application the information in the search came from.