How to add resource files in in /src/main/resource after deploying mule application in mmc - mule

I have just deployed for the first time a mule application in Mule management console(MMC),after deploying I want to add csv file in src/main/resourses/input folder. where can I find path and add csv file to that path.

You can see the below image for details.
In other words,
Click on Servers tab --> Server --> Files tab --> apps --> Select your application --> classes --> Click on New File button --> Upload file.
But I suggest, keep your file in some other location and read it instead of keeping with in application folder structure.Problem is if you re-deploy the app from MMC, whatever files you have added manually from MMC will be deleted as MMC will take application from repository and deploy into server whenever you do re-deploy.

{MULE_HOME}/apps/{my app}/classes/{input folder}
Any folders under src/main/resourses will reside under the classes folder found in your app folder, which is under the apps folder of the standalone Mule server.

You could look at this path
/opt/mule-standalone-3.7.0/apps/{appname}/classes

Related

Persistent Axis2 Service Files

I deployed an instance on Axis2 within my JBoss EAP 6.2 server. However, the only way I can add my service files are through the online admin console. This is a problem because when I add them through the console they are added to a random folder within standalone/tmp/vfs. So when I stop and start my server again I lose my reference and I need to re-add them through the console. How can I set it up so that I do not need to re-add my service files every time I start my server?
You can prepackage them inside your war under /WEB-INF/services so that they are automatically deployed with the war file.
e.g.
/WEB-INF
/services
/service_a.aar
/service_b.aar
/services.list
The services.list file in the same directory is a text file listing your aar files ... one per line
The aar files are just zipped Axis archives. They contain a META-INF directory with your wsdl, any xsd files and an Axis2 services.xml service configuration file describing the service.

MobileFirst: Back-end service discovery wizard not appearing - single wsdl with multiple xsd files

I have a wsdl & multiple xsd files.
When I copy them inside the services folder of a MobileFirst project. Then it does not show/detect them inside the services folder. It shows as empty folder when viewing in Project Explorer view. However it does show wsdl & xsds files when viewing through Package Explorer.
I want to run the Back-end service discovery wizard to generate the adapter functions, rather than manually typing the SOAP messages in adapter functions.
Currently it is not showing the option of Back-end service discovery wizard
You do not need to copy the wsdl and xsd files into the services folder. You should be able to run the Back-end service discovery wizard off the services folder and then point to those files on your file system.
The project explorer view only shows elements under the services folder that are representations of the underlying service model (as defined in the service descriptor xml files). It does not show the xml files themselves or any other file types, but just shows nodes that represent a service model node. This was done only for the project explorer view. You can view the service descriptor xml files and any other file types in other viewers such as the navigator viewer or package explorer. It is assumed that the only files that would ever be in the services folder would be the service descriptor xml files. It is not necessary that you put your files under this folder.

Mule ESB - moving mule application logs to different location

I am planning to move mule application logs which are generated in ${MULE_HOME}/logs folder to D:\logs.
I tried changing the configuration element in ${MULE_HOME}/conf/wrapper.conf file as follows.
wrapper.logfile=%MULE_BASE%/logs/%MULE_APP%.log
But its only copying single log file that is mule.log.
Is there any way we can move all the logs to a defined location?
Thanks in advance.
Do you have log4j.xml or log4j.properties file defined for your application. Change path in that

Use WLST to Retrieve Local Application Path

I am currently automating a process of moving Weblogic applications from old servers to new servers. I was unable to find a way to list the local application path for a deployed Weblogic application using WLST. The closest I found was:
appInfo=cmo.getAppDeployments()
for app in appInfo:
app_path = getPath(app)
print app_path
which will return something like:
InternalAppDeployments/test.war
This is not the directory I am looking for. I was wondering if someone had some input on how to retrieve the local directory for deployed Weblogic applications.
One easy way to do it with WLST:
ls('/AppDeployments') # this will list all of the deployments
cd('/AppDeployments/<app name>')
cmo.getAbsoluteSourcePath() # this will list the full path
Some things you could try instead of WLST:
Navigate to the /config/ folder and do a:
grep source-path config.xml
This will list the full path to the deployment IF that deployment was deployed with nostage staging-mode. Those paths will be relative if the deployment was deployed with stage for the staging-mode, it will be copied to each managed server that was targeted for the deployment and you will get relative paths like you mentioned above...
Those ear/war files likely live under:
<domain>/servers/<server name>/stage/<deployment name>
Or under
<domain>/sbgen

Hot deployment of modified axis archive for web services

Apache axis2 (1.6.1) support hot deployment of web service archives when copied to axis war's web-inf/services folder. But this is limited to new services only. It does not hot deploy 'changed' services .. does anyone have a solution for handling 'changes' in the service archives ?
-abhay
Just figured out a way to do this. Instead of 'over-writing' the service archive file, do a delete and copy of the archive file. Deleting the archive from the web-inf/services directory forces axis to automatically 'undeploy' the services and then adding the changed archive is treated as a 'new service archive' and is automatically deployed.