Calling X++ from sql server

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.

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.

Multiple AX Environments

Discovered an easy way to switch between multiple AX environments....you have to have seperate configuration files. the hard way of course is to use the Configuration utility and then set the location you want to connect to be the top connection and then lauch AX. Having 2 different shortcuts is a lot easier.

One of the items in the configuration file is a startupmsg so that you can tell what environment you are going to and another is for the AOS location. Just set these items and away you go.

You can use the Configuration Utility to setup the configuration files and then export them to a folder location. Once there you then change the shortcut so that it will use a specific configuration file when it loads.

SSRS 2008 Grant Database Error

WOW....this should not be this hard. I am upgrading our SSRS from 2005 to 2008 so that we can use the tablix and some graphs in out reports. After I had installed everything (in the right places mind you) I could not grant database access. "Unable to connect to the Report Server WMI provider" ...I read tons of post about it being security and this and that. Well I never imagined that the security it was talking about was hosting the central admin on the SSRS server! Thanks to Bruce Van Buren (http://znetsys.spaces.live.com/blog/cns!ED65D09C41E55E06!165.entry) I realized the errors of my ways and it is now fixed. I am pretty sure that when I roll this into production I did not want my Central Admin sitting on my SQL 2008 IIS box. One of the cool things about (at least I thought) about SSRS 2008 was the new architecture. Removing IIS and using SQL server network stack and http.sys (http://www.devconnections.com/updates/LasVegas_07/SQL_Connections/Welker_SQL%20Connections_SMS315_What)

Sharepoint and SSRS...I won

Finally figured it out and have the SSRS running on one of our WFE's. It should be noted that we have a medium farm for about 70 users. We have 2 WFE's that are load balanced, hitting a SQL cluster. Our Farm is pretty underused...OK it is way overkill for the amount of users we have and the the amount of users that are actually using it. The machines are beasts and we averaging something like 80 distinct users and 375 hits a day.

I figured out that I had to give my users distinct rights to the reporting services folder. Thanks SSRS for the help

Sharepoint and SSRS

Sometimes you just have to wonder why it is not easier. I mean what I want to do should not be difficult...I just want SSRS to be on WFE in my Farm. Should be easy right. It took me a while in QA to get it installed because it would not connect through Sharepoint. I struggled and struggled but it would not bring up the Server Defaults on the Central Admin. Finally this solved it... http://blogs.msdn.com/feldman/archive/2007/11/18/quick-guide-on-how-to-install-reporting-services-on-its-own-server-cluster-in-sharepoint-integration-mode-without-using-kerberos.aspx . Today we are moving SSRS for Sharepoint into production. But where???? Sql cluster not really where I want it since I will need an IIS server on the SQL box. Why not the WFE. So far so good except when applying SP 2 I am going to have to do a reboot. Once this is done lets up it works pretty quick and easy.