We have a problem with our production install of IS 6.0.2 which I am hoping you have seen before, or know how to get around.
We have established 4 discrete IS environments � Development, System Test, User Acceptance Testing, and Production. Each of these is a separate install of IS, has a separate Broker, and a separate Oracle instance accommodating the Xref, ISCoreaudit, ProcessAudit, and TN functional pool.
We are running Oracle 8i on a hpux11i platform. We have Trading Networks, Modeller, and additional components including WmebXML.
The Development, System Test and User Acceptance Test environments were all created on a single server. The installation and configuration went very smoothly, and all environments functioned.
We then performed the Production implementation on a separate server, but did not have a chance to start IS as we were waiting on our Database Administrators to create the file system and empty schemas. Due to a server upgrade we then migrated the 3 non-Production environments to the same server the Production server is hosted on.
These three environments can start and run successfully.
The problem is with the Production implementation. We started IS and did the usual configuration � Broker names, Extended fields, and jdbc pool and functions. We then shutdown and restarted IS�this is when our problems started.
When IS first starts up and realises it has a database to talk to, it recognises that the schema is empty of records and populates these with the initial processing rules and document types you see when you first start TN. This process, as seen in a log with DEBUG set to 10, appears to load up 11 records into the ProcessingRules table�and then it stops functioning. Almost. Every 120 seconds it writes about 10-15 lines to the server log talking about Repository entries and then goes to sleep for another 120 seconds. It does not get past this point. It does not get as far as starting the HTTPListener on the primary port.
At this point we�ve had to crash the server by giving it a �kill� message. After removing the LOCKFILE and restarting, IS goes through the motions of checking the Repository, and then starts loading records from the database again. It gets to the stage of giving us a message saying �loading Processing Rules��and stops again. No loops, just sits there.
What have we tried? Lots:
Dropped and recreated the Oracle database tables. No luck.
Deleted and recreated Oracle on the file system. No luck.
Substituted the empty Oracle database for one we had prepared on another system. This worked, in that IS started, but it is beside the point. We should be able to load IS with an empty database the way that webMethods intended it…
Took the same substituted database, dropped its tables and recreated them. No luck.
Dropped tables and recreated schemas, then pointed our (working) User Acceptance instance of IS at it to populate. No luck (interesting this�you would think that a working IS install would go through to completion�this has us suspecting our Oracle install�)
Dropped tables and recreated schemas. Disabled the TN functional pool and restarted IS. This worked, but as soon as we added in the TN pool and restarted IS�no luck.
Deleted the WmRepository2 folder under IntegrationServer/config. (in case this was corrupt) No luck.
Started IS without a database. Disabled the WmebXML package. Dropped tables and recreated schemas. Restarted IS. This worked, in that database records were created and IS could restart�but when we restarted WmebXML and restarted IS�back to square one.
So � that is where we are at. Point 3 is the closest we have gotten this thing to run up. My suspicion is that there is something different in terms of Oracle install, or unix patch level, on the particular server we are running on which is causing jdbc problems between IS and the Oracle database, causing these lock ups and failures. I have our systems admin guys looking into this. My next and most annoying step to take is to blow away the entire Production installation � databases, executables, repositories, and packages � and reinstall it from scratch. I really don�t want to have to do that.
If you have seen such behaviour in IS when it is first running up, I�d really appreciate hearing what you believe caused it, and what you did to resolve it.
Thanks in advance,