Trying to use the Service Discovery feature of MobileFirst Platform Studio 7.1.0.00-20160323-1606.
The adapter.xml file that gets generated is for an HTTP adapter, not an SAP adapter.
<wl:adapter xmlns:wl="http://www.ibm.com/mfp/integration"
xmlns:http="http://www.ibm.com/mfp/integration/http"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
name="SAPGWAdapter1">
That also creates the connectionPolicy tag as <connectionPolicy xsi:type="http:HTTPConnectionPolicyType">
This doesn't allow me to add properties that were included with the xsi:type="nwgateway:NWGatewayHTTPConnectionPolicyType" type definition, like <serviceRootURL> and the <serverIdentity> nodes.
Can I change the adapter type back to SAP, or is HTTP the standard now? If it is, how do I pass in the serverIdentity properties? Trying to test the adapter against a live SAP instance is giving me "Unauthorized" errors (at least, I think that's what it says. It's in German...)
-Paul Horan-
We still offer SAP adapters. Use whichever adapter best fits the task.
Create a new Adapter, if you are using the eclipse plugin then right click on adapters > new > MobileFirst Adapter
Under adapter type you have two options
SAP Netweaver Gateway Adapter
SAP JCo Adapter
here is our user documentation on SAP adapters
Related
We need to create a scalable application with a single instance of DB connection used across adapters , possibly want to use Spring hibernate for the same - how can we use mfp v 8 to implement such a use case.
would like to use the spring context to use common service beans across adapters
I do not believe you can use it across adapters, as each adapter lives in its own sandbox. You'll need to add it to each adapter separately as a maven dependency in its pom.xml file.
I am new to Mule and followed this blog to create a "websphere-mq connector" through the jms connector. I am using the community edition.
In order to connect to the websphere mq server, I must run the application under a specific Windows username. Running the mule application in Mule Design under the specific username, I am able to connect and receive messages. However, I am unable to connect to the websphere mq server through the standalone application running on a windows server. I changed the user on the service that is running mule to the specific user but am unable to get authorization to the websphere mq server.
Any additional insight would be much appreciated.
I would suggest reviewing the "Getting going without turning off security" article for an introduction to MQ security. This might help get the MQ system correctly configured.
The stand alone application runs the Tanuki Software wrapper as the user assigned to the environment variable %USERNAME% in windows. Even though I updated the user in the Mule service to run as the approved user, the wrapper will take the environment variable.
To solve the problem, I updated the wrapper.conf file to include the following:
set.USERNAME=<approvedUsername>
the environment variable %USERNAME% is now set to the approved username, in which mule will allow the JMS connector to the authenticate with the correct username.
We are trying to implement proxy service using WSO2 ESB (4.8.1). The proxy service implementation needs to access wsdls, schemas and xslts.
One option is to put these artifacts in Governance registry. However, we are not planning to connect ESB with database (which is recommended for governance registry). In that case, is there a way I can refer to these files that are residing in the file system along with other ESB artifacts?
Thanks,
You can use the concept call Deployment Synchronizer based on SVN. Deployment Synchronizer provides capability to synchronize deployment artifacts across the nodes of a product cluster.
I like to call a flow from another project in Mule. Is that possible.
If its so please provide me the details how it can be achieved?
Thanks in advance.
If they are separate projects(even on the same JVM) then you cannot use flow-ref but will have to use a transport such as JMS, HTTP etc. If you are using Mule 3.5 Enterprise Edition then you can use the VM transport to communicate between projects using the new shared resources and domain functionality. More info on that here: http://www.mulesoft.org/documentation/display/current/Shared+Resources
We have more than 5 corporate applications running on different servers with technologies like spring, struts communication between these application is point to point. We are planning to migrate this to ESB using Mule.
I didnt quite understand how mule works i have few doubts,
Mule is running in a different server do i need to deploy all my 5 aplications into the mule server.
I have spring application delployed on a tomcat server how this application is going to receive messages through mule or what are the configuration changes i need to do in my server or mule server.
Any advice or tutorials.
You need not deploy all you 5 applications in the Mule Server.
You said that all your application are currently point to point (which means that all are talking/communicating now through http protocol), similarly you can also use mule's http endpoints to communicate with all the 5 applications.
I.e. the spring application talking to another spring application can be modified to Spring application talking to Mule and Mule in turn talking to another Spring application .
You must learn the basics from the Documentation
http://www.mulesoft.org/documentation/display/current/Mule+Fundamentals --> browse through the navigation on the lefthand side.
Mule is an integration tool. you no need to change any of your existing applications. All you need is to develop an mule application which can do the mediation/orchestration.
For connecting with your spring application you no need to change any configuration you need to use http:outbound connector inside your mule flow
Just go through http://www.mulesoft.org/documentation/display/current/HTTP+Transport+Reference
So mule is based on SOA principle, so your 5 corporate service need not to be their in a single system. so if you want to consume the service/functionality of any of your 5 application, expose those service as web service, cloud be soap or rest. And you can call those service inside your mule. so in this case you have to create only 5 connection and where ever required you can refer to those connection inside mule configuration file.
#saravanan shanmugavel you need to use Mule ESB to orchestrate the communication between these application...ESB came into the picture to remove your point to point communication...you can create a proxy service for each of your service and one flow which will orchestrate communication between all...
All you need to do is change the application that is configurable according to mule server.
Please refer below link that will be helpful for understanding of mule that helps you better orchestrate communication between all.
https://docs.mulesoft.com/