%SelectSQL

Indicates its a metastorm select Query example: %selectSQL(select * from database.dbo.table)

How to fetch Errors in Metastorm

Go to Metastorm BPM from start Menu >> Service Manager >> Connect Metastorm Database >> Diagonostics >> Designer Log >> Procedure Maps Also a lot of services you can find here

Tips to remember

While designing maps, don’t give roles to Actions instead keep (tick) ‘to do list’ While designing forms, ‘custom variable’ is important for control (you can set it from the property of control) Action. Notes: Some thing related to fetching data(we ll discuss it later)

SQL - Metastorm

What ever tables come with prefix ‘e’ in table name inside Metastorm database are system tables. Don’t play with that tables, it may corrupt Metastorm suite. Some of them we are going to discuss here. Efolderid: which is important, based on this id the Metastorm is connecting tables and relationships.So we can call it like a control point Ealert : this table is used to find who all are in watch list and who are in to do list, inside this table there is a column named ealerttype, If ealerttype=~, then it is watch list =blank, then it is in to do list =!, Metastorm don’t know which stage it is(that’s why exclamation, just wondering) Efolder: it is treated as master control. estage: indicates whether the process is in which stage right now. Note: After publishing your procedure, you just explore through these tables. You can realize directly what actually happens inside and what the relations between these tables are and how Metastorm is using these tables for smooth functioning

Basic Things in Metastorm

There are three basic things :-Stage, Action and Role. Stage: Place where the action is going to happen. Action: An action is needed to pull you from one stage to another. Role: who have the power to do the action There are six stages in Metastorm 1. Group stage: Where the decision is taken by a group of people. 2. Common stage: where the user can do some common actions 3. Archive stage: where you can finish the process (just like an end point/repository) 4. System Stage: Decision making stage, can specify condition inside this stage Ex: If you don’t want to process if the cheque is not less than 1000, in this case we can use this stage. Like if cheque <1000> 5. Sub procedure stage: Here we can set flag for some criteria, so that the procedure will call the sub procedures and return to the parent procedure after doing something in sub procedures required by the criteria. 6. User stage: Decision is taken by a single person.

How To Install LiveCycle 8.2.2 with MSSQL 2005

This article is designed to aid in the manual installation of LiveCycle 8.2.2 with MSSQL 2005. Attached is a zip file with all the files that I reference that should be easily dropped. This article was intended to create development environments. JBossService_64-bit.zip LiveCycle-JBoss-MSSQL -Install.zip Install JVM Install JDK 1.5.0.12. Create JAVA_HOME environment variable under "My Computer | Properties | Advanced" and point to your JDK installation folder. Install Database Install MSSQL 2005. The only thing you need to install is "Server" and "Client/Workstation" components. Create a database called "lc_es". Run the 6 attached scripts (*.sql) in order against the "lc_es" database. These scripts will prepare your database for Configuration Manager. These scripts will create a user called "lc_db_usr" with a password "password". NOTE: some SQL installs don't let you use "password" as a password so you will have to search and replace this password in all the files from step 6 below and the files in this step. Install LiveCycle 8.2.2 Unpack the LiveCycle install files to "C:Installs". Install LiveCycle 8.2.2 using "Manual". Stop before you run configuration manager (LCM). Let the install hang here. Install JBoss Copy "C:InstallsAdobe_LC_ES_JBOSS_WIN_8.2third_partyjboss" folder to the "C:AdobeLiveCycle8.2" folder. For JBoss 4.2.0 on 64-bit Windows 2003 copy "C:InstallsAdobe_LC_ES_JBOSS_WIN_8.2third_partyjboss_4.2.0" to "C:AdobeLiveCycle8.2" and rename "jboss_4.2.0" to "jboss" Copy attached "JBossService.exe" to the "C:AdobeLiveCycle8.2jboss" folder. For JBoss 4.2.0 on 64-bit Windows 2003 you will need to use the 64-bit version of "JBossService.exe" which is also attached here. Run "InstallJBossService.bat" to install JBoss as a Windows Service. For JBoss 4.2.0 on 64-bit Windows 2003 you will need to copy "C:InstallsAdobe_LC_ES_JBOSS_WIN_8.2third_partyjbossInstallJBossService.bat" to the "C:AdobeLiveCycle8.2jboss" folder. For JBoss 4.2.0 on 64-bit Windows 2003 you will need to add "-b <your jboss server ip address>" to the parameters in "InstallJBossService.bat" before you run it. Find "-c all" and add it immediately after this. If the IP address changes you will likely have uninstall the Windows Service, change the IP address in "InstallJBossService.bat" and rerun it. To uninstall change "-install JBoss for Adobe LiveCycle ES" to "-uninstall JBoss for Adobe LiveCycle ES" and remove all the parameters after that. Deploy LiveCycle Run LCM past the step where it configures the LiveCycle components for deployement and then STOP there (at the LiveCycle ES Database Initialization screen). Copy files from the EAR files from the "C:AdobeLiveCycle8.2configurationManagerexport" folder to the "C:AdobeLiveCycle8.2jbossserveralldeploy" folder. Configure JDBC Datasource for LC and JMS Copy attached "sqljdbc.jar" to the "C:AdobeLiveCycle8.2jbossserveralllib" folder. Copy attached "jbossmq.jar" to the "C:AdobeLiveCycle8.2jbossserveralllib" folder. For JBoss 4.2.0 on 64-bit Windows 2003 ignore this step. Copy attached "mssql-ds.xml" and "adobe-ds.xml" to the "C:AdobeLiveCycle8.2jbossserveralldeploy" folder (replace existing file). Delete the file "C:AdobeLiveCycle8.2jbossserveralldeploymysql-ds.xml". Copy "standardjbosscmp-jdbc.xml", "login-config.xml", "standardjaws.xml" to the "C:AdobeLiveCycle8.2jbossserverallconf" folder (replace existing files). For JBoss 4.2.0 on 64-bit Windows 2003 copy ONLY "standardjbosscmp-jdbc.xml" and "login-config.xml" to the "C:AdobeLiveCycle8.2jbossserverallconf" folder (replace existing files). Copy "mssql-jdbc2-service.xml" and "mssql-jdbc-state-service.xml" to the "C:AdobeLiveCycle8.2jbossserveralldeploy-hasingletonjms" folder. For JBoss 4.2.0 on 64-bit Windows 2003 copy "mssql-jdbc2-service.xml" and "mssql-jdbc-state-service.xml" to the "C:AdobeLiveCycle8.2jbossserverall deploy jms" folder. Delete "mysql-jdbc2-service.xml" and "mysql-jdbc-state-service.xml". Start "JBoss Run Configuration Manager Finish running LCM. That's it courtsey : Brad White

Generate XSD from XML

There are several tools out there to create (or to infer) an XSD schema from XML document. I liked trang command line tool the most. Found it first when reading about Spring web services in Spring in Action book (very good book btw). Here are four simple steps how to create XSD from XML* using trang: Step 1. Get trang Download trang.zip from here (at the moment of writing “trang-20030619.zip”) Step 2. Extract it Use “unzip trang-version.zip”, or just winzip/winrar/7z etc.. if on windows Step 3. Make an alias This step is optional, but makes it extremely easy to run the tool with a single command. Make an alias to the “trang.jar” by (in my case Ubuntu/Linux) editing “~/.bashrc” and adding the following: # execute trang.jar (create XSD from XMLs) alias xml2xsd='java -jar ~/soft/utils/trang/trang-20030619/trang.jar' above “~/soft/utils/trang” is the directory where “trang” was unzipped to. Step 4. Create XSD from XML Let’s look at the XML file we need an XSD for: $ ls -l total 4 -rw-r--r-- 1 user group 357 2008-05-28 15:38 holiday-request.xml   $ cat holiday-request.xml <?xml version="1.0" encoding="UTF-8"?> <holidayRequest xmlns="http://mycompany.com/hr/schemas"> <holiday> <startDate>2006-07-03</startDate> <endDate>2006-07-07</endDate> </holiday> <employee> <number>42</number> <firstName>Ultimate</firstName> <lastName>Answer</lastName> </employee> </holidayRequest> now run the tool against it: $ xml2xsd holiday-request.xml hr.xsd $ cat hr.xsd <?xml version=”1.0″ encoding=”UTF-8″?> <xs:schema xmlns:xs=”http://www.w3.org/2001/XMLSchema” elementFormDefault=”qualified” targetNamespace=”http://mycompany.com/hr/schemas” xmlns:schemas=”http://mycompany.com/hr/schemas”> <xs:element name=”HolidayRequest”> <xs:complexType> <xs:sequence> <xs:element ref=”schemas:Holiday”/> <xs:element ref=”schemas:Employee”/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=”Holiday”> <xs:complexType> <xs:sequence> <xs:element ref=”schemas:StartDate”/> <xs:element ref=”schemas:EndDate”/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=”StartDate” type=”xs:NMTOKEN”/> <xs:element name=”EndDate” type=”xs:NMTOKEN”/> <xs:element name=”Employee”> <xs:complexType> <xs:sequence> <xs:element ref=”schemas:Number”/> <xs:element ref=”schemas:FirstName”/> <xs:element ref=”schemas:LastName”/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=”Number” type=”xs:integer”/> <xs:element name=”FirstName” type=”xs:NCName”/> <xs:element name=”LastName” type=”xs:NCName”/> </xs:schema> done! $ * – NOTE: “trang” can create an XSD from multiple XML documents, not just one. List of other tools to use as an alternative to trang: xmlbeans: http://xmlbeans.apache.org/docs/2.0.0/guide/tools.html#inst2xsd online tool: http://www.flame-ware.com/xml2xsd/ oxygenxml: http://www.oxygenxml.com/ (eclipse plugin: http://www.oxygenxml.com/eclipse_plugin.html) stylus studio: http://www.stylusstudio.com/autogen_xsd.html XSD away, Good Luck! Courtsey: dotkam