Publishing Near Tool as a GP Service in ArcGIS Server 10 - arcgis

I am curious if someone has successfully published Near Tool as a service. This tool is located in Analysis Tools > Proximity. The tool updates the input layer it doesnot have an output layer. I am not sure if this possible or if there is a workaround.
Appreciate any ideas.
Thanks
Jay

Jay,
all tools have an output. If you don't see one in the user interface it is because it is considered a derived parameter/output. For more information please take a look at http://resources.arcgis.com/en/help/main/10.1/index.html#//018z00000063000000.
Once you place the tool inside a model you can specify the inputs and outputs explicitly. The complete sharing workflows are outlined and detailed with screen captures at http://resources.arcgis.com/en/help/main/10.1/index.html#//005700000047000000
Thomas

Related

Is there any Static Code Analysis Tool to verify API REST guidelines?

Thanks in advance for sharing your ideas and inputs.
We know there are many REST guidelines for API published these days. I use the below for internal code review.
https://github.com/Microsoft/api-guidelines/blob/master/Guidelines.md
Is there any way I can automate the code review against the guidelines? Is there any specific tool for the same?
If no, can any of the available tool be configured with custom rules to check against the guidelines?
Any inputs are highly appreciated.
Thanks, Neel
I am using SwaggerHub which has built in standardisation checking but am playing with spectral to automatically review / lint against our standards.
API handyman/Arnaud Lauret
has an excellent series on how to do this and how spectral can be used to be an "Augmented API reviewer"

What are the main points that must be documented for a data integration project?

I am working on a data integration project using Talend.
I have many input sources heterogeneous, I make transformations and I save output data to many output sources. Actually, I am doing Extraction, Transformation and Load (ETL).
My Talend Job is executing everyday on a linux server (the production). I have a development and test environment on a windows VM, ... In fact, I have many things I want to document and I don't really know how. I used to document web development projects (just the frontend), but not data integration projects.
Can you guys help me with some keywords, examples, templates, so that I can make a clear documentation for my client ?
Thanks in advance :)
While I can't speak to your organizational needs, Talend is designed to be largely self documenting. If you were diligent in filling out the documentation and descriptions in your job, you can right click the job and select 'Generate Doc as HTML'.

Mule SOAP to SOAP integration scenario

Is there any way, compatible with computer science rules, to make at list 2 flows in one project like this:
External system 1 -> SOAP endpoint (mule) -> java object -> transformation -> java object -> SOAP endpoint (mule) -> External system 2.
Our non working solution:
single flow
We experience bug [www.mulesoft.org/jira/browse/MULE-5926]. Yes I read [stackoverflow.com/questions/25744541/mule-issue-more-than-one-jaxbcontext].
The solution which has nothing in common with the ESB philosophy but has one major single advantage, it works: looks like looks like this
Some helpful resources:
[www.enterpriseintegrationpatterns.com/patterns/messaging/] - notice please there are separate router and translator components.
Any ideas?
Best Regards, Apologies I can post only 2 links due to my reputation rank.
The reason the last image works is more about what you cannot see. Just visually seeing the Java component on the MuleSoft canvas (screen where you "draw" the flow or integration solution) doesn't provide enough detail as to what the Java component is doing. And, while the icons on the canvas are nice, we generally inspect problems by looking at the XML.
Your question is not clear. The flow that you described in your image can't be discerned into an integration pattern I recognize and the details behind your flow design are vague.
Please provide your Mule config (XML) for the same flow, but first try to edit your question to explain exactly what you are trying to do. Stackoverflow is a place where problems are identified and problems are resolved. It's also a place for the history of what we do. It is up to us to do our homework before we add new questions. Myself or maybe someone else will help you but only after you clearly explain your problem. Yes, other solutions work but there's no way I can compare your flow to the simple one with the Java component without a LOT of background information.

Data flow visualisation

I'm searching for a program where I can visualize all my data flow. I've made a simple example:
Is there a way how I can visualize all the data. I've found examples of "Prefuse" and "Flare". But there's too much to add to the examples. Isn't there a nice program wich has it all?'
it's preffered when I can connect the data to a database. So the whole process will be automated.
it's preffered when I can collaps/uncollaps the systems and application flow(e.g. when I click on an application, the arrows appear).
I hope someone can help.
you can use Graphviz (http://www.graphviz.org/) for creating the vizualization.
for the database connection, you could use a programming language to generate the input to the graphviz program.
I had this same problematic and used a combination of SAS and Graphviz to solve it.
hope that helps.

test a monitoring tool

please guide me how to test a monitoring tool?
Due to the nature of the project (a program that monitor another target program), we cannot expect the input (activity of target program) and hence what is the best way to test it?
I don't know exactly how your monitoring tool is working, but I think that some how it communicates with some 'target' applications, retrieve data from them and displays a report.
I think that your problem is that you cannot control the input to your monitoring tool, in order to test that it displays correct data, because that input depends on your target apps.
My suggestion is to create a Mock application. This app must have the same interface with your real target app so your tool can communicate with it. Of course, the implementation must be different. Implement it with that way, so that every parameter is checked by your tool will be configurable to you. So, you will be able to know which will be the input to your tool.