As part of our implementation I was trying to figure out how to call X++ classes from within sql server stored procedures. The purpose behind this was to help integrate with our Allen Bradley machines on the shop floor. We did not use this method but I thought it was really neat that I could make all of the calls this way if needed....
I wrote a SQL Assembly file that when called from a trigger fires the stored procedure that connects to a web service. The web service calls CallStaticClassMethod to get the class, method and params.
More to follow.
Tuesday, August 16, 2011
To deploy or not to deploy
Discovered that there is another way to deploy EP stuff today. We are getting close to "go live" and I did a code push of the var and cus layers today in production. After I jumped through the hurdles and then ran AxUpdatePortal it continually failed. I then remembered I needed to be on the sharepoint server for it to run correctly, at least that is what I think I did last time. It runs! Of course I check to make sure everything is there but there are not current changes and an epupdate log with nothing in it.
After messing around for a few hours I discovered that if I manually deployed my proxies to the correct location and then manually deploying from the AOT everything appears to be there. I am curious as to what is not there and what did not get pushed out correctly. So far in my preliminary testing everything seems to be there.
In the AOT right click on \Web\web files\web controls and there will be a selection for Deploy.
Guess I know how I am going to deploy everything...manually.
Subscribe to:
Posts (Atom)