I am using mule esb to transfer file from ftp to local directory. I am not using the standard FTP connector but the extended one.
I am getting an error:
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://localhost/schemaftpext/mule-ftpext.xsd'.
Actually I am new to Mule ESB, so i do not what is the url "http://localhost/schemaftpext/mule-ftpext.xsd" says that. I need to put anything in localhost?
FYI: I am using the example "http://code.google.com/p/mule-ftpext/source/browse/trunk/Test/mule-config.xml?spec=svn23&r=23". What should i do for that localhost URL?
http://localhost/schemaftpext/mule-ftpext.xsd is just a schema URI location: there is no need to have anything available there, it is just used as an identifier. Mule's configuration loader will resolve this URI to an actual location at load-up time. The actual location is within ftpExt-1.0-SNAPSHOT.jar.
Now this implies that you need to have is the ftpExt-1.0-SNAPSHOT.jar available in Mule's classpath. Is that the case?
Related
I'm using Apache Camel in a project and when I needed to use the camel-ftp component to send some files to an remote server, I've got this exception:
com.jcraft.jsch.JSchException: Session.connect: java.security.NoSuchAlgorithmException: DH KeyPairGenerator not available
I was wondering why it could be happening in my project. So, I've started a quick small project with camel-core and camel-ftp components only and I pasted the route there and it worked fine.
from("file:data/input?noop=true")
.log("Uploading file ${file:name}")
.to("sftp://www.mydestination.com:22/../opt/tmp?autoCreate=false&username=MyUser&password=MyPassword&passiveMode=true")
.log("Uploaded file ${file:name} complete.");
I'm using Apache Karaf to run OSGI Bundles (my application is one of them). I've checked in different environments but the result still beeing the exception.
I really don't know what it could be. Anyone has some ideas about what can be the possible cause of it?
DH KeyPair Generator is normally part of the JRE/JSE and should be included if your JDK (>BTW which exact JDK version are you using ?).
Given that, your error is probably due to a wrong classpath.
I suggest you to check the value of "-Djava.ext.dirs" property (and the contents of the corresponding folders), for instance:
Windows:
java -Djava.ext.dirs="C:\Program Files\Java\jdk1.6.0_07\jre\lib\ext;C:\dir2"
Unix:
java -Djava.ext.dirs=$JAVA_HOME/jre/lib/ext:/dir2
You also need to specify/modify the Karaf security provider, take a look at:
https://karaf.apache.org/manual/latest/security
apache server is used for static contents. We are able to GET required resource having fully qualified path:(e.g. http://cmsTest.com/content/otp.txt). However, now we need to scan all folder available under
http://cmsTest.com/content
I need to access directories available at particular location via Spring REST GET api. When I am trying to access(http://cmsTest.com/content) it, getting 404 error.
Could you please provide suggestion for the same?
I am getting this exception when i am trying to start the WAS server. I have created JMS providers in console and set all the jar files in the classpath.
External initial context factory defined is com.sonicsw.jndi.mfcontext.MFContextFactory with a valid URL.
I am not sure if the issue is with websphere configuration settings or code.
Can someone please provide any context to move forward?
Can you add more information?
classpath, properties set up for your connector
check this documentation :
http://documentation.progress.com/output/Sonic/8.5.1/jca_books/resadapwas_guide.pdf
regards
Does anyone know how to put/load configuration files required for a target in Apache ACE other than configurator? I am using apache configurator to pick .cfg files from conf directry but i always get the error:
*ERROR* Unexpected problem providing configuration xxxxx to service [xxx, id=xx, bundle=xx/osgi-dp:xxx]
Does anyone knows how to fix this?
The configurator bundle was designed to provide configuration via "cfg" files to the ACE server, relay and client. It was not designed for provisioning configuration data to a target. From your question, it looks like you are trying to do that, so...
For doing that, ACE supports the Auto Configuration Service as described in chapter 115 of the Compendium. In short, that specification uses configuration files in an XML format. These files, along with the resource processor, then get provisioned with the end result that the configuration data is sent to the Configuration Admin service automatically. More documentation about that process, and using "template" configuration files (in case you need to configure many targets with only a few differences between them) is described here:
http://ace.apache.org/user-doc/user-guide.html#using-the-template-engine-for-targets
I am trying to install EAR file with EJB module on IBM WAS 7.0.0.27 by using WSADMIN-wsInstallApp (for automation). but its getting below error
**WASX7109E: Insufficient data for install task "MapResRefToEJB.**
But the same ear file can be deployed manually by IBM console.
it looks ejb mapping reference issue. i tried so many ways but couldnt get the solution.
can anyone please suggest for a solution.
Code
target name="installEAR"
wsInstallApp ear="${earFile}" options="-appname ${application}" wasHome="${wasHome.dir}" profileName="${profileName}" conntype="${connType}" port="${port}" host="${hostName}" user="${userId}" password="${password}" /target>
Try:
options="app-name ${application} -usedefaultbindings"
If you actually want to specify bindings, you'll need to replace -usedefaultbindings with -MapResRefToEJB ..., where the options you specify need to be formatted based on the wsadmin scripting language you're using (jacl or jython). See the InfoCenter for a full AdminApp options, including -MapResRefToEJB and -MapModulesToServers.