The documentation on page 297: Configuring_PMMs_Connectors_and_Agents.pdf
AdminUser — The name of the Microsoft SQL Server administrative user that can log on to the SQL server. This user must be a SQL login user, a member of the SQL Server SECURITYADMIN fixed server role, and the DB_ACCESSADMIN database role.
- I am told it does support named instances.. such as Server\Instance, but since I am not yet able to establish a connection, I cannot verify this. *When you get the connector to work, it works as show.
- Basically, your server has to be mixed mode, and the privileged account must be a SQL (not windows, not domain) account
- There is a configuration parameter that is not mentioned in the documentation…IgnoreAccessGroup. I don’t have a clear understanding of what this is, and I don’t know if it’s ok to leave this unassigned. (*When you get the connector to work, it will tell you valid settings are yes or no)
- I am using the same configuration information that I used to set up the PMM, which is working, so I know that I have the correct user name and password, BUT I cannot get the AMM to configure correctly. I keep getting an “unable to verify connection”. *You need the patch below.
The Connector and PMM for Microsoft SQL Server depend upon the SQL-DSO activeX object, which is no longer distributed with the SQL Server client that is packaged with SQL Server 2008 and 2008 R2. To address this missing dependency, download and install Microsoft SQL Server 2005 Backward Compatibility Components on the Courion Server, or on the CF/CFM machine running the Connector/PMM accessing SQL Server 2008. This assumes you have installed the SQL Client Software, as directed in the prerequisites for the Connector/PMM for SQL Server:
The SQL Server client must be installed on each server in which the Connector
Framework or Connector Framework Manager is installed. Note that the SQL
Server Management Studio Express client cannot be used—you must install the
regular SQL Server client.
Microsoft SQL Server 2005 Backward Compatibility Components are packaged with the Microsoft SQL Server 2008 Feature Pack, available at the following Microsoft Downloads location:
Microsoft SQL Server 2008 Feature Pack, August 2008
http://www.microsoft.com/download/en/details.aspx?id=16177
Just a list of tools that are handy to use with Courion….
The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.
Here’s an excerpt:
A New York City subway train holds 1,200 people. This blog was viewed about 4,200 times in 2011. If it were a NYC subway train, it would take about 4 trips to carry that many people.
Click here to see the complete report.
http://opensource.com/life/11/11/introduction-kdenlive
I found the default identitymap *.xslt (ACCreateFormCtrls.xslt) to be a bit complex…with something like 30 (maybe more) imports. Which one of the 30 to edit? making sure you don’t break something else, etc.
However, there’s a simpler way.
There is an *.xslt called BuildIdentityMapCtrl.xslt, which is very monolithic.
I simply made a copy of this file, and pointed the identitymap screen to this copy, and deleted out the information we didn’t want. Now I have an *.xslt file that is less than 400 lines long, and doesn’t import any other files… Simpler to debug, modify, and, yes, comprehend.
After a request has not been approved, we wanted to send out an email nagging the person saying that the request has, effectively, timed out and they need to do something. I could not find a suitable criteria inside of the courion workflows to accomplish this, so I did it inside of SQL server.
First off, set the time out comment inside the workflow to say “Timeout …..” (I just used the first 7 characters, so you can make the rest of it whatever you want it to say. I have blanked out the approval steps in the following screen shot.
Next, create a database trigger, so that when an approval step’s comment field is changed to “Timeout….”, a record gets created in another table with the information. This second table (MailsToBeSent – based on a article on the internet which I have now lost the link to) will then be used as a basis for emails going out via an SSIS process. Here is the trigger.
USE [ILM]
GO
CREATE TRIGGER [dbo].[SAP.Request.Add.Timeout]
ON [dbo].[ApprSteps]
AFTER UPDATE
AS
IF UPDATE (Comments)
Insert into [ILM_PROFILE].[dbo].[MailsToBeSent]
([MailID],[From],[TO],[CC],[BCC],[Subject],[Body],[IsHTMLFormat],[Priority],RequestID,DateTimeAdded)
VALUES
(
(SELECT MAX(MAILID)+1 from [ILM_PROFILE].[dbo].[MailsToBeSent]),
(SELECT [ParameterValue] FROM [ILM_PROFILE].[dbo].[ConfigurationParameter] where ParameterName =’NoReplyFromEmailAddress’),
‘noreply@company.com’,'noreply@company.com’,'noreply@company.com’
–’subject’
–,(SELECT REQUESTID from INSERTED),
,’Request Escalation’
–’body’
,’This is to inform you that request no. ‘ + CAST((SELECT REQUESTID from INSERTED) AS VARCHAR(10))
+ ‘ for user creation is still pending after ‘
,’True’,1
,(SELECT REQUESTID from INSERTED)
, GetDate())
GO
http://virtualrouter.codeplex.com/
Depending on what your ticketing table looks like, here you go…
Select ‘<TR><TD>’ as EXR0, Date,’</TD><TD>’ AS EXR1,UserActedOn,’</TD><TD>’ AS EXR2,TargetID,’</TD><TD>’ AS EXR3,ActionReturnMessage,’</TD></TR>’ AS EXR6 from ticketing
where Date >CAST(SYSDATETIME() as datetime) -.04
order by Date desc
This will give you only the results for the last hour (0.04 days)
http://www.ehow.com/how_2160460_custom-iphone-ringtones-free.html
