Received bad status 302 on server request to update managed asset

-
After installing BPM 8.5 release 6, following error occurs when trying to upload a server file on Process Designer:

alt text

The ProcessDesignerInstallationDirectory\workspace.metadata.log shows:

!ENTRY teamworks.appserver.websphere 4 0 2015-06-10 12:33:53.028
!MESSAGE
[com.lombardisoftware.server.ejb.repositoryservices.ManagedAssetsClientAPI createManagedAssetAE] CWLLG2212E: Received bad status 302 on server request to update managed asset

cd <BPM Dir>/bin
./wsadmin.sh -connType NONE -lang jython

 wsadmin>bpdServer=AdminConfig.list("BPMProcessCenter").split()

 wsadmin>bpdServer

 ['(cells/PCCell1/nodes/Node1/servers/server1|server-bpm.xml#BPMProcessCenter_1385413578191)']

 wsadmin>print AdminConfig.showAttribute(bpdServer[0],'useHTTPSURLPrefixes')
 false

 wsadmin>
 wsadmin>AdminConfig.modify(bpdServer[0], [['useHTTPSURLPrefixes', 'true']])
 ''

 wsadmin>print AdminConfig.showAttribute(bpdServer[0],'useHTTPSURLPrefixes')
 true

 wsadmin>AdminConfig.save()






Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more