Recent Posts

81

Content Navigator / Issue connecting to ICN Repository

« Last post by jsquizz on February 22, 2024, 01:03:15 PM »

Fresh install of ICN / WAS / DB2 / CMOD /etc - on a windows 2022 environment

We try linking a CMOD repository, and are seeing this error in the websphere log.

2/22/24 12:47:35:858 MST] 00000095 SystemOut     O CIWEB Error: [admin@server] com.ibm.ecm.struts.actions.od.ODLogonAction.createODConnection()
com.ibm.edms.od.ODException: Failed to initialize the GSKit. Ensure proper installation of the GSKit and configuration of the environment.
at com.ibm.edms.od.ODServer.logon(ODServer.java:1032)
at com.ibm.edms.od.ODServer.logon(ODServer.java:934)

But, when we look in the system log - We see a login from ODWEK/The user we're trying to use for the repo.

Has anyone seen this? We verified classpath/path/java/etc

82

MP Server / Re: arsmaint has stopped working post CMOD upgrade from 8.5 to CMOD 10.5

« Last post by Ed_Arnold on February 19, 2024, 01:18:32 PM »

mayank - are you good now?

Ed Arnold

83

MP Server / Re: arsmaint has stopped working post CMOD upgrade from 8.5 to CMOD 10.5

« Last post by mayank81089 on February 18, 2024, 12:53:27 AM »

Understood system is working as expected.

Cache expiration is run using the arsmaint -c command.
OnDemand will expire storage objects from cache if all of the following conditions are met:
The maximum cache threshold is reached for a cache file system. This is specified when you run arsmaint with the '-x' parameter. The default value is 80%.

84

MP Server / arsmaint has stopped working post CMOD upgrade from 8.5 to CMOD 10.5

« Last post by mayank81089 on February 17, 2024, 11:59:52 PM »

Hello,

We have observed that since we have gone live with CMOD 10.5.0.5 which was an upgrade from CMOD 8.5 the arsmaint utility is not working. As the cache storage size has increased exponentially, we have TSM client node registered as our archive storage solution however we are also maintaining one copy of the documents inside cache folder as well that is for 90 days only. We tried opening documents which have been stored in CMOD for more than 90 days but still see them coming from cache node instead of TSM client node. are there any changes in the utility command parameters in new version?  prior to upgrade it was working fine

checked the permission and ownership of arscache/cache1 folder and everything seems correct as per IBM documentation.

parameters used in arsmaint command -cdrs

documents are not getting flushed from cache folder.

Thanks,
Mayank

85

OD/WEK & JAVA API / Re: ODWek REST - response HTTP 408 - No availble connections to pool <poolname>

« Last post by Andreas Baaserud Hauge on February 12, 2024, 12:54:31 AM »

 Hi, thanks for reply

Our problem was firewall related. ODWek REST not able to connect to CMOD Library Server.
Solved by opening in firewall

86

z/OS Server / Re: CMOD 10.5 Release Notes

« Last post by Ed_Arnold on February 08, 2024, 02:01:48 PM »

At 10.5.0.7 the default TLS (SSL) level for both clients and the server flips from TLS V1.2 to TLS V1.3.

If implementing TLS for the first time, things might be easier if all of CMOD, clients and servers, are at 10.5.0.7 first.

87

MP Server / Re: CMOD roadmaps after V10.5

« Last post by teera_aoo on February 07, 2024, 10:24:05 PM »

Thank you very much everyone. I will convince end customer to go 10.5.

88

MP Server / Re: Can we skip Post Processor Script when loading with Generic Indexer?

« Last post by rjrussel on February 02, 2024, 09:16:22 AM »

I am fairly certain that you can't, but I am still looking. I'll let you know if I find something. In the meantime, while not a great solution, you could create a copy of the APP without the postprocessor defined. Again, not great, but depending on what you are doing might be better than nothing.

89

MP Server / Can we skip Post Processor Script when loading with Generic Indexer?

« Last post by Mehmet S Yersel on February 02, 2024, 08:54:51 AM »

Hi All,

I am loading migration data from a CMOD 9.5 into a target CMOD 10.5 system using Generic Indexer. For migrated reports, I need to skip the PostProcessor.sh script because these reports already have been processed with the PostProcessor.sh script. However, Day forward reports need the post processor to populate some index fields upon ingestion for the first time.

I know, normally, migration reports need to go to a separate AG and day forward reports need to go to separate AG. But, client didn't want this option. They want to load into same AG both day forward as well as migration data.

Second alternative is to manipulate the script. I am loading from a Windows platform into Linux. So, modifying the post processor script to distinguish between the 2 data types wouldn't work because the file paths and script names cannot be the same for Windows (where migration data is loaded from) and Linux (where day forward data is loaded from) platforms. If loading of migration reports starts from a Linux platforms, same as day forward reports, this method would work. But that doesn't look like a viable option due to time it would take to set up.

Third alternative is to add new applications for migration data, remove post processor scripts and load migration data this way.

But, ideally, I should be able to tell ARSLOAD to skip Post Processor Script for a particular report. And I don't see this option being available (maybe an enhancement request). Is there a way to skip a post processor script for a certain report without having to remove it from Load Instructions?

Thanks in advance,
-Mehmet

 

90

MP Server / Re: CMOD roadmaps after V10.5

« Last post by Ed_Arnold on February 02, 2024, 08:37:20 AM »

This is inquiry from customer. Because they decision for upgrade project, and inform that if we go 10.5 and EOS in next year, this will not worth to upgrade it.

Hello Teera - I occasionally get asked about CMOD plans and directions.

First off - nobody tells me anything, and I don't want to know, either.  That way I can maintain plausible deniability about CMOD plans and directions.  :-)

What I do when asked is point people to this official doc:

https://www.ibm.com/support/pages/how-do-ptf-numbers-relate-content-manager-ondemand-product-version-numbers-and-maintenance-fix-packs

It's written for z but the information is true across all platforms.  All service fixpacks, all announcement and end-of-service dates are in lockstep across the CMOD platforms.

You can see that 10.5 is the only currently supported release.

No announcement has been made (yet) about a follow on release.

I believe that an announcement of support has always given a customer two years to upgrade.

No announcement has been made for 10.5 EoS so at a minimum there would most likely be two years to upgrade.

CMOD 10.5 is currently at fixpack 7 (10.5.0.7).  While it really means nothing note that 9.5 and 10.1 put out several more semi-annual fixpacks during their lifecycle.

One thing I can say is that new function lately has been pushed out via fixpack, so read those fixpack announcements thoroughly!  :-)

Anyway, I absolutely recommend upgrading to 10.5.  Get to a supported environment.

Ed Arnold