Tibco packaging, publishing, and running

Here we will record some of the troublesome issues of tibco 5.6 release (lin49940 original ).

1. There is no problem with the test mode process. An error occurred while running after the release.

Check the registration namespace of the process. Whether it is the main process or sub-process, this is very troublesome. If it is more than enough, it will not work if it is wrong!

Basically, in the test mode, tibco helped us block these registration namespace errors. However, after the process is released and run, these problems will be exposed !! In many cases, we reference a schema and delete the schema reference to restore it to the state before the reference. However, this is because the schema has been registered in "schema Imports, if this schema conflicts with another schema2 to be referenced later, an error will be reported when parsing the XML control referenced by schema2 !!!!

Focus on controls"Parse XML"If there are multiple "Parse XML" controls in our process, and the "outer Editor" of these controls reference the same schema namespace, we may reference These schemas, the namespace specified by tibco is used,Except that the first referenced schema will be registered in "schema Imports", other schemas will not be registered in "schema Imports ".,
Because their namespaces are the same, tibco thinks they are all the same and no longer register !!!! In this case, there is no problem in the test mode, but after the release, when the process runs to these "Parse XML" controls, an error is reported !!!The solution is to manually register these Schemas to "schema Imports.

2. There is no problem with the test mode flow, and the timer and JMS receiver cannot be left or right!

I still have no reason for this. It seems to have a lot to do with the project itself! I tried to package and release a timer process in a project, but the timer does not work. I copied the process to another project for packaging and publishing, the timer runs properly !!!

Tracking the problem again. I established a simple timer process in the project, run once, package and release, and run successfully !! It proves that the timer in this project is valid, but some controls have problems !!

There have been countless tests and the reason is that there is a problem with the Database Control !!!

1. The names of those connections reference the global variables of the "password" type, rather than the text of the "string" type!

2. Delete the connection links set for those database controls, apply, and set the connection link again. Remember to change them all, although it is very troublesome !!!!!(Required)

After these two steps, my timer process will finally be executed after being packaged and released !!! But I'm not sure if Step 1 is necessary, but step 2 is necessary !!!

Since the original process is not backed up, we cannot compare it before and after (each process is in XML format, and many details cannot be seen in the designer, use XML to compare the content.) wait a year and compare the two processes to find out the reason !!!!!!!!!!

I have found out the cause, yesThe link path is case sensitive !!!

Connections such as JMS, FTP, HTTP, and JDBC are referenced by controls such as JMS receivers and JDBC queries. for example, the actual directory of a jdbc connection is/AAAA/xxjdbcconnection, however, the reference path in a database query control is/AAAA/xxjdbcconnection (this control may be directly copied from other projects ),
In test mode, no problems will be tested !!! However, after packaging and publishing, the running process can be "running", but there won't be "Created processes". Many times we think the process is "running, however, this process does not actually work properly !!!!!!!!

3. In the test mode, you can read the shared folder of the LAN machine, but cannot access the shared folder after publishing.

The cause of this situation has a great relationship with the user of the tibco background process !!!

If tibco registered services "tibco administrator 5.4 (XXX)" and "tibcohawk agent (XXX)" in windows are not modified. By default, the default users of these two services are system. Generally, we do not log on to system users, and system cannot directly access shared folders, the user name and password are required for access !!!!

In test mode, our current user can access the shared folder and save the user name and password for accessing the shared folder so that the shared folder can be accessed directly next time! The tibco file control does not provide the username and password required to access the shared folder. Therefore, you can only save the username and password of the shared folder, then, the tibco file control can directly access the shared folder.

Therefore, we need to modify the user of the "tibco administrator 5.4 (XXX)" and "tibcohawk agent (XXX)" service processes to our current user, which is generally administrator. The changed operation is completed in the operating system. "Computer Management" -- "" service "-" bring up the properties page of related services "-" click "Log on"-"to select this account, fill in the user name and password in the key, and save-"to restart all tibco items.

Run the post-release process again. There should be no problem !!!

4. An error occurred while running all the released tibco processes.

Here, we should pay attention to the timer process. If the timer process cannot be terminated, or the execution time exceeds the interval, resulting in an increasing number of processes, the entire tibco background process will report an error, unable to run! Therefore, you must be careful when designing the timer process. The controls in the process must have time-out settings at the end.