Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - mroutlander

Pages: [1]
1
MP Server / SSL Connectivity Working Inconsistently
« on: October 09, 2020, 05:35:57 AM »
Hi fellow ODUsers,
I am experiencing a strange problem. My client is running 9.5.0.11 as the CMOD server (on AIX v7 TL5). Recently, the SSL certs expired and so we got a new signed one and installed it per the IBM documentation. Checking with openssl and gsk8capicmd_64 both, the certificate and its validity appears fine.

Now comes the weird part - when connecting the Administrator client (running on Windows Server 2012) using the SSL port (1446), it goes through and the connection is established. However, the Viewer Client (running on Windows Server 2012) refuses to connect with the same settings. The ubiquitous error - "Connection cannot be established..." is seen in this case. Am I missing something trivial?

An associate of mine is trying to connect from the Administrator Client on the same machine as mine, but he is not able to connect. This has left us all quite befuddled.

Side Note - I enabled the trace at server and client ends but can't seem to find the trace file anywhere. At the server, the file is named ARCHIVE.trace.log but a search for this filename fails. Trace level is 15 and ars.cfg file has been updated too. Where could it be?

2
Hi fellow techies,

I am trying to connect to an SQL Server 2017 [the chosen database for CMOD] installation on Windows Server 2016 from CMOD 10.5 [Library server] on Red Hat Enterprise Linux 7.7 box  (both on Azure cloud). Could you please help me understand:

1. If it is possible and has anyone implemented it?
2. What are the prerequisites at both ends?
3. Any kind of separate ODBC setup required on the the library server box?
4. Any other considerations?


I admit that a remote database isn't the ideal setup but we are doing it to enable MS Support (Azure, you see  :D ). IBM documentation doesn't give any clear answers including the mandatory prerequisites and configurations (ars.cfg, ars.dbfs etc.).
 
https://www.ibm.com/support/pages/creating-remote-microsoft-sql-server-database-ibm%C2%AE-content-manager-ondemand


Apologies if this looks like a noob question. Any help shall be really appreciated. Thanks

3
Hi fellow ODUsers,
I have been facing a typical problem with document breaking. I had an existing report layout (for EBCDIC reports) being indexed using ACIF. Per the new revisions mandated by the customer,
1. The positions of some of the fields changed a little
2. For some other fields, the width changed a little
3. Two fields got added.

So, I made these minor changes to the Indexer code, no biggie. Now to the weird part - earlier the same (well, almost) indexing scheme used to split a multi-page document to multiple single-page documents based on the change in field values E.g. a 3-page document would be split into 3 separate documents of 1 page each and each of the documents would have the correct index values saved against it in the database. If the OutletID field is populated as 0133, 0149, 0157 on three different pages, it appeared likewise in the indexes. But now:

1. Three rows get created but no split actually happens. All the three documents contain all the three pages
2. The index values populated for the first document are correct (picked from the first page) but these values are also duplicated for the second and third documents. i.e. OutletID 0133 is getting populated for the other documents too. Likewise for other fields. Only the ProbationDate field changes now (it is based on a floating trigger)

Code: [Select]
CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
MCF2REF=CPCS
TRC=NO
FILEFORMAT=RECORD,133
TRIGGER1=*,1,X'F1',(TYPE=GROUP)                                                                           /* 1                */
TRIGGER2=2,61,X'C3E3D940C6C9D3C540D9C5D7D6D9E3',(TYPE=GROUP)                   /* CTR FILE REPORT  */
TRIGGER3=*,37,X'E5C9D6D3C1E3C9D6D540C4C1E3C5407A',(TYPE=FLOAT)                 /* PROBATION DATE : */
FIELD1=1,3,10,(TRIGGER=1,BASE=0)
FIELD2=4,17,3,(TRIGGER=1,BASE=0)
FIELD3=6,17,10,(TRIGGER=1,BASE=0)
FIELD4=4,54,8,(TRIGGER=1,BASE=0)
FIELD5=4,90,8,(TRIGGER=1,BASE=0)
FIELD6=7,17,100,(TRIGGER=1,BASE=0)
FIELD7=0,54,8,(TRIGGER=3,BASE=0,MASK='########',DEFAULT=X'F0F1F0F1F1F9F7F0')   /* 01011970         */
FIELD8=8,23,5,(TRIGGER=1,BASE=0)
FIELD9=5,17,9,(TRIGGER=1,BASE=0)
INDEX1=X'C49683A4948595A3C481A385',FIELD1,(TYPE=GROUP,BREAK=YES)                  /* DocumentDate     */
INDEX2=X'D98583969984E3A89785',FIELD2,(TYPE=GROUP,BREAK=YES)                          /* RecordCategory      */
INDEX3=X'E28598A485958385D5A494828599',FIELD3,(TYPE=GROUP,BREAK=YES)           /* SerialNumber   */
INDEX4=X'C396A58599818785C2',FIELD4,(TYPE=GROUP,BREAK=YES)                            /* CheckStartDate        */
INDEX5=X'C396A58599818785C5',FIELD5,(TYPE=GROUP,BREAK=YES)                            /* CheckEndDate    */
INDEX6=X'E2A482918583A3D5819485',FIELD6,(TYPE=GROUP,BREAK=YES)                    /* SubjectName      */
INDEX7=X'E589969381A3899695C481A385',FIELD7,(TYPE=GROUP,BREAK=NO)              /* ProbationDate     */
INDEX8=X'E2A3969985C9C4',FIELD8,(TYPE=GROUP,BREAK=YES)                                  /* OutletID  -position changed          */
INDEX9=X'C2A4A2E49589A3',FIELD9,(TYPE=GROUP,BREAK=YES)                                 /* BusinessUnit  - new field         */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=GROUP
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE

How the indexes appeared earlier:
DocumentDate   OutletID    RecordCat  CheckStartDate  CheckEndDate     SlNo      Subject                ProbationDate
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-02-26                   
2016-03-02       0149       3A           2016-03-20      2016-03-26      00002   ILVEA GOMEZ ZALAYA        2016-03-26                   
2016-03-02       0157       4A           2016-04-20      2016-04-26      00003   ILVEA GOMEZ ZALAYA        2016-04-26


How are they appearing now:
DocumentDate   OutletID    RecordCat  CheckStartDate  CheckEndDate     SlNo      Subject                ProbationDate
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-02-26                   
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-03-26                   
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-04-26   

What could I be missing? Any help will be really appreciated.

Regards,
AP

4
MP Server / Updated CMOD version Not Reflecting with arssockd -I ARCHIVE -q
« on: December 05, 2018, 04:34:51 AM »
Greetings everyone,
We recently upgraded CMOD (installed on one of our AIX 7.1 systems) from v9.0.0.3 v9.5.0.11. All the pre-requisites were met and the installation steps went fine on the day of the upgrade and when I used arssockd -I ARCHIVE -q it showed me the correct version number (v9.5.0.11). All the relevant symlinks and paths were updated too.

However, when I logged back into the system today and queried arssockd -I ARCHIVE -q again, it threw the old version number (9.0.0.3). I checked if any of the scripts/symlinks/environment variables were still pointing to 9.0.0.3. It was found that the PATH variable in $HOME/.profile was pointing to the 9.0 setup. I rectified the same but am still seeing the old version on querying.

Weirdly enough, when I miss the -q flag, the system outputs the upgraded version:

Code: [Select]
/home/adminod > arssockd -I ARCHIVE | head -20
ARS0980I Usage: arssockd [options]
        Version:  9.5.0.11
        -h <od_inst> OnDemand instance name or host name (same as -I)
        -I <od_inst> OnDemand instance name or host name (same as -h)
        . . .
        . . .

What might be wrong/missing? Any suggestions will be much appreciated.

EDIT: When I invoke arsload to ingest a standalone file, the server version comes up as 9.0.0.3. This is crazy  :-X

Code: [Select]
/arsacif/filestobeloaded > arsload -h localhost -I ARCHIVE -u adminod -p xxxxx -g AGNAME -a AppName AGNAME.AppName.20181205.063536.ARD

2018-12-05 06:44:38.808252: ARS4334I Load Version <9.5.0.11>  Operating System <AIX> <7.1>  OS Userid <ADMINOD>  Install Location </opt/IBM/ondemand/V9.5/> Data(unlimited KB) Stack(unlimited KB) Core(0 512-blocks) Cpu(unlimited seconds) File(unlimited 512-blocks) Nofiles(unlimited) Threads(262144) Processes(262144)
2018-12-05 06:44:38.808300: ARS4335I Server Version <9.0.0.3> Operating System <AIX> <7.1>  Database <DB2> <10.05.0010>
....
....

Also, the same set of installation steps were performed on another server (the QA box) and it is absolutely fine. Displays the correct version number too (with arssockd -I ARCHIVE -q)


Warm regards,
AP

5
MP Server / Weird Error: The application group >< does not exist
« on: April 26, 2018, 09:25:08 AM »
Greeting fellow ODUsers,

I am facing a strange and baffling error for the past three days. I set out to process 111 odd reports using the arsload daemon. While 107 of those got processed successfully, I am facing the following error for the remaining 4:
Code: [Select]
The application group >< does not exist or user >ADMIN< does not have permission to access the application group
That "><" is essentially weird because the appgroup in question does exist and ADMIN does have administrative permissions on it. The report format is standard across the 111 reports -
Code: [Select]
AG.APP.IGN.IGN.ARD
OS: AIX 7.1.0.0
CMOD: CMOD for Multiplatforms 9.5.0.9

What could be going wrong? Any help would be really appreciated.
Thanks and Warm Regards,
AP

6
Hello everyone,
We have a web application running  ODWEK 7.1.x (yeah, I know it's quite old, please don't judge me  :D :P ) connecting to CMOD 7.1.x. Thing is, we are trying to upgrade the setup. CMOD server upgrade was successful and we are able to use it perfectly through the Thick Client.

However, the web application that uses ODWEK for CMOD connectivity, uses classes - ArsSVTInterface and ArsWWWResultand it's there that we are having troubles. Now we could modify the application if we knew what actually these classes entail but we haven't found a single piece of documentation on these. The idea is to remove any references of the former (as IBM suggested) and update the code with correct usage of the latter.

Decompiling the classes doesn't give much of an insight. Could you please help me understand these classes, or suggest a workaround?

EDIT: Forgot to mention, CMOD server is on 9.5 and ODWEK intends to be there.

Warm regards,
Abhinav

7
MP Server / Editable Index field/values in an AppGroup
« on: June 24, 2016, 06:21:23 AM »
A warm hello to fellow ODUsers,

I need a little help. My client wants to make certain index fields/values modifiable in a particular app group - let's say fields InvNumber and InvAmt in a certain AG called InvoiceUpdate. These should be editable for a certain group only - say ZonalManagerGroup.

While I understand that this process would start somewhere from the AG permissions tab and/or the ARSAGPERMS table. But I am not sure where and how to begin it?

Any assistance will be appreciated. Please let me know if I haven't furnished any other required information.

Warm regards,
Abhinav

Edit: Forgot to mention: this is for CMOD on Multiplatforms v 9.0.0.3

8
OD/WEK & JAVA API / ODServer code is non-responsive
« on: April 16, 2015, 04:28:46 AM »
Hi all,

I have been facing a very typical problem. When connecting to a remote CMOD server from a standalone program, I am able to get through but when the same is being tried through a web application, it gets stuck.

ODServer instance never gets created and of course never gets initialized.
Code connecting to OD (works just fine in the standalone program):
                     odConfig=new ODConfig();
         odServer = new ODServer(odConfig);
         odServer.initialize("RetrieveODDoc.java" );
         System.out.println( "Logging on to the CMOD server...." );
         odServer.setPort( 1445);
         odServer.setServerName( "ServerName" );
         odServer.setUserId( "Username" );
         odServer.setPassword( "Password" );
         odServer.setConnectType(ODConstant.CONNECT_TYPE_TCPIP);
                     odServer.logon(); 
   

On the web application side, it just doesn't respond  :'(
                             odConfig = new ODConfig();
      System.out.println("OD Config is fine");
      odServer = new ODServer(odConfig);
      System.out.println("If you see this, ODServer is fine");
It just doesn't seem to get past line 2.

Env. details: ODWEK 9.0.0.0, Java 1.7.0_65 (64-bit) , Win 7 Enterpise 64-bit client, Win Server 2008 R2 Enterprise (64-bit) CMOD Server, Eclipse Juno 64-bit (IDE)

Any assistance will be much appreciated.
Thanks in advance

Pages: [1]