Hello @LL,
I was able to install PA 3.1.4-TP. Here are my observations:
TM1 12: Installation went almost smoothly (I was using Rocky 9 Linux):
- edit /etc/os-release and change PRETTY_NAME="Red Hat Enterprise Linux 9", otherwise you will get error complaining about getting 3rd party components (mongo and other stuff)
- disable selinux
After that you get pretty funny named services running :) :
- /opt/ibm/tm1/bin/tm1sd.exe
/opt/ibm/tm1/third_party/datastore/mongod
/opt/ibm/tm1/bin/tm1-gateway.exe
/opt/ibm/tm1/bin/async-handler.exe
/opt/ibm/tm1/bin/authorization.exe
/opt/ibm/tm1/bin/tm1-daemon.exe
/opt/ibm/tm1/bin/batch-handler.exe
After installer finishes, you'll get connection details for TM1: Service Instance URL, Client ID and Client Secret.
Installation of PAW (ipa_workspace_local_3.1.4.359.zip) is event simpler (using Rocky 9 Linux):
- install podman (dnf install podman)
- run ./Start.sh
There is no admintool container nor admintool.sh script. Probably documentation need to be corrected or it hasn't been implemented yet.
This is the moment where I am stuck. Don't know how to connect from PAW Local to TM1 12. Already tried setting TM1LoginServerlURL using Service URL from TM1 12, but cannot authenticate (how to pass client id and client secret?). Do I need to use external OIDC provider? Documentation is not clear (I know its TP :)).
There is also a way to authenticate using older TM1 release (you can use CAM for instance). But after configuring, keep getting error in tm1-gateway:
{
"level": "error",
"date": "2026-01-26T13:59:55.568Z",
"message": "Instance specified in the URL not found.",
"service": "tm1-gateway",
"version": "12.5.5",
"instance": "api",
"logger": "apiLogger",
"stacktrace": "github.ibm.com/TM1/logzap.(*Logger).parseLog\n\t/root/go/pkg/mod/github.ibm.com/!t!m1/logzap@v0.7.0/logger.go:243\ngithub.ibm.com/TM1/logzap.(*Logger).Error\n\t/root/go/pkg/mod/github.ibm.com/!t!m1/logzap@v0.7.0/logger.go:273\nmain.(*server).authHTTPPassthroughHandler\n\t/workspace/app/tm1/services/tm1-gateway/server_authentication_http.go:180\nmain.(*server).authOIDC_HTTP\n\t/workspace/app/tm1/services/tm1-gateway/server_authentication.go:176\nmain.(*server).authHandler\n\t/workspace/app/tm1/services/tm1-gateway/server_authentication.go:221\nmain.(*server).authenticationHandler\n\t/workspace/app/tm1/services/tm1-gateway/server_authentication.go:113\nmain.(*server).initialize.(*server).main.func7\n\t/workspace/app/tm1/services/tm1-gateway/server.go:184\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2322\ngolang.org/x/net/http2/h2c.h2cHandler.ServeHTTP\n\t/root/go/pkg/mod/golang.org/x/net@v0.43.0/http2/h2c/h2c.go:125\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:3340\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:2109"
}
Maybe this helps someone :)
Cheers!
UPDATE: 2026-02-03
I didnt catch it earlier, but you also need an OIDC provider. You just need to install it by yourself. I used keycloak (How to Install KeyCloak IAM in Rocky Linux 9.6)
And you are good to go :)
Thanks @Hubert Heijkers and @STUART KING for your help.
Cheers.
------------------------------
Pawel Romanek
------------------------------