FN PE tools vwlog vwtool pelog in container

petool.sh

#PE Tools on container
# 1. Downlaod IBM FileNet Process Engine >> PE Java API from ACCE
# 2. also CE for jace.jar

#create jre or jdk pod

kind: Pod
apiVersion: v1
metadata:
  name: tilo-jdk-pod
spec:
  containers:
    - name: tilo-jdk-container
      image:  registry.redhat.io/ubi8/openjdk-17 #no runtime to have TAR for copy
      #image: registry.redhat.io/ubi8/openjdk-17
      #image: registry.access.redhat.com/ubi8/openjdk-17
      command:
       - sh
       - -c
       - while true ; do echo alive ; sleep 3600 ; done
      
	  
######################
## on Pod Run: 	  

#create top level folder
mkdir fn-pe-tools && cd $_

# create config folder and config (modify for your URL)
mkdir config
cat <<EOM >config/WcmApiConfig.properties
RemoteServerUrl = http://vf2-cpe-svc:9080/wsi/FNCEWS40MTOM/
CredentialsProtection = Clear

CredentialsProtection/UserToken = Symmetric
CryptoKeyFile/UserToken = 
EOM


##copy PE jar files (run on host with oc/kubectl cli)
kubectl cp /mnt/c/Users/tilo/Downloads/PE-tools/lib/ tilo-jdk-pod:/home/jboss/fn-pe-tools/
##need petools.jar pe3pt.jar and Jace.jar (from ACCE client downlaod)
##got petools from traditional install


##make PE datadir
mkdir  peDataDir

##set VAR
JPEDATA_DIR="peDataDir"
JPEINSTALL_DIR=$PWD

##call Java (modify with your CP and user, remove -Y part to get prompted)
java -cp "lib/petools.jar:lib/pe3pt.jar:lib/Jace.jar" -DJPEINSTALL_DIR="$JPEINSTALL_DIR" -DJPEDATA_DIR="$JPEDATA_DIR" -Djava.security.auth.login.config="$JPEINSTALL_DIR/config/jaas.conf.WSI" -Dfilenet.wcmapiconfig="$JPEINSTALL_DIR/config/WcmApiConfig.properties" filenet.jpe.vwtool.VWTool CP1_OS1 -v -Y "cp4baadmin+MyPass"