Profound Logic Forums

It´s possible to install profoundui inside IASP directory? I try to start and application from profound but file objets are inside IASP and can not find them.

Any ideas? thanks!!

Giovanni,

It is possible to run Profound UI in an IASP. We do have some customers that are running it that way. The only trouble is, our installer does not currently know how to install into an IASP, so you have to install it into *SYSBAS and then manually move it and reconfigure the Apache server appropriately.

Basically to do so, you would:

1) Install into *SYSBAS
2) Move the library (named PROFOUNDUI by default) into an IASP
3) Edit the Apache configuration in /www/profoundui/conf/httpd.conf to point to the proper IASP.

The Apache config changes would need to provide the proper IFS path to point to the new IASP. For example, right now we have configuration options that look like this: You'd need to modify them to point to the IASP, for example: There are quite a few similar directives that you'd have to modify like that. Then, it should work in an IASP. It's just a bit of a pain to go through and set all of this up by hand because our installer doesn't currently do it for you.

If you wouldn't mind giving us some feedback...

The reason the installer doesn't do it for you is simply that in the early days of the product, we didn't have much demand for IASP support. As a result, we at Profound never got very familiar with the IASP support, etc. So when the installer was written, it just forced things into *SYSBAS and doesn't have options to ask you for an ASP group or anything like that.

We (the Profound Developers) had a meeting about this about a month ago because we have been seeing more demand for IASP support recently. In fact, another customer had asked the same question that you're asking. So we are trying to decide if we should change the installer, and what sort of changes we should make. Here's what we were thinking:

1) The installer would still default to *SYSBAS, but...

2) When you click the 'customize' button during installation, there'd be a place to specify a different ASP group. (Currently this customize button lets you select things like library name, http server name, http server port, etc. So this would just be another field on that panel.)

3) If you selected something in the ASP group field, it would create the library in the appropriate IASP, and automatically set up the httpd.conf file for that IASP.

Do you think that sounds like a good solution? Would that work for you if we implemented it in a future release?

Thanks!

Hi! I´ve followed all steps and It has not worked.

I have copied profoundui directory into IASP and I have modified 'httpd.conf' file, to point to new location.

I have restarted profound and when I lunch session, it throws the following exception:

The program has encountered an unmonitored exception. Please contact the system administrator for assistance.Message Id:PUI0005Severity:40Date:2014-06-20Time:17.41.30Program:PUI0001200Procedure:Initialize__FvLine(s):1343Message:Unable to start the application job.Cause . . . . . : The controller encountered an error while attempting to start the application job. The detailed error message is: 3025 - No existe tal vía de acceso o directorio.

I attach my configuration file. I am not sure if I´ve done all changes needed. Please, do a review and confirm me. Thanks a lot!




# Uncomment the following to use SSL.
#LoadModule ibm_ssl_module /QSYS.LIB/QHTTPSVR.LIB/QZSRVSSL.SRVPGM
#SSLEngine On
#SSLAppName YOUR_SSL_APP_NAME

LoadModule proxy_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
LoadModule proxy_http_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
LoadModule proxy_connect_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
LoadModule proxy_ftp_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
# Uncomment the following if using LDAP authentication.
#LoadModule ibm_ldap_module /QSYS.LIB/QHTTPSVR.LIB/QZSRVLDAP.SRVPGM

ErrorLog /www/profoundui/logs/error_log
LogMaint /www/profoundui/logs/error_log 7 0

DefaultNetCCSID 1208
DefaultFsCCSID 284

Listen 8080

AddType application/genie .scn
AddType application/genie .lst
ExpiresByType application/genie A2592000

ThreadsPerChild 40
MaxCGIJobs 1000
MaxPersistentCGI 1000

#The following control session timeout and should all be set to the same value.
SetEnv PUI_TIMEOUT 3600
MaxPersistentCGITimeout 3600
Timeout 3600

# Controls purge interval for expired session DB records. Give value in hours.
SetEnv PUI_SSN_PURGE_INT 2

Options -Indexes -Includes

DocumentRoot /www/profoundui/htdocs

ScriptAlias /profoundui/atrium/menu /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0003000.PGM
Alias /profoundui/atrium /www/profoundui/htdocs/profoundui/userdata/html/atrium_login.html
Alias /profoundui/changepass /www/profoundui/htdocs/profoundui/userdata/html/change_password.html
Alias /profoundui/start.html /www/profoundui/htdocs/profoundui/userdata/html/start.html

ScriptAliasMatch ^/profoundui/PUI000(11.{2}|1200|2.{2}|3.{3}|4.{3}|50.{2}|91.{2})(.*) /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI000$1$2
ScriptAliasMatch ^/profoundui/auth/PUI000(1200|21.{2}|91.{2})(.*) /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI000$1$2
ScriptAlias /profoundui/auth/start /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0005001.PGM
ScriptAlias /profoundui/auth/genie /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0002100.PGM
ScriptAlias /profoundui/designer /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0001100.PGM
ScriptAlias /profoundui/viewdesigner /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0001100.PGM
ScriptAlias /profoundui/universal /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0001114.PGM
ScriptAlias /profoundui/genieadmin /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0002200.PGM
ScriptAlias /profoundui/genie /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0002100.PGM
ScriptAlias /profoundui/atrium /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0003000.PGM
ScriptAlias /rpgsp /QSYS.LIB/RPGSP.LIB/
ScriptAlias /profoundui/welcome /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0004000.PGM
ScriptAlias /profoundui/start /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0005001.PGM
ScriptAlias /profoundui/ipademulator /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0005001.PGM
ScriptAlias /profoundui/iphoneemulator /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0005001.PGM
ScriptAlias /profoundui/key /IASP/QSYS.LIB/PROFOUNDUI.LIB/PUI0004100.PGM

SetEnv PUI_UPLOAD_CAP 100

ProxyPass /php/ http://127.0.0.1:10088/
ProxyPassReverse /php/ http://127.0.0.1:10088/

<Directory /IASP/QSYS.LIB/PROFOUNDUI.LIB/>
AllowOverride None
SetHandler cgi-script
Options +ExecCGI +Includes
SetOutputFilter Includes
RewriteEngine on
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
</Directory>

<DirectoryMatch "^/IASP/QSYS\.LIB/PROFOUNDUI\.LIB/PUI000(11.{2}|22.{2}|4.{3})\.PGM">
Require valid-user
AuthType Basic
AuthName "Profound UI"
PasswdFile %%SYSTEM%%
UserID %%CLIENT%%
</DirectoryMatch>

# This environment variable must be set to match the value of
# your AuthName directive. This is used by the Atrium sign on
# program to sign users into the correct "realm".
SetEnv PUI_AUTH_REALM "Profound UI"

# The following sections control how authentication is handled in Profound UI.
# To change the authentication procedures, comment/uncomment the desried sections.

# Use the following section for IBM i profile authentication.
<DirectoryMatch "^/IASP/QSYS\.LIB/PROFOUNDUI\.LIB/PUI000(3.{3})\.PGM">
Require valid-user
AuthType Basic
AuthName "Profound UI"
PasswdFile %%SYSTEM%%
UserID %%CLIENT%%
ProfileToken On
</DirectoryMatch>

<LocationMatch "^/profoundui/auth/(.*)">
Require valid-user
AuthType Basic
AuthName "Profound UI"
PasswdFile %%SYSTEM%%
UserID %%CLIENT%%
ProfileToken On
</LocationMatch>

<FilesMatch "^PUI000(9106|1113).PGM">
CgiConvMode binary
</FilesMatch>

# Use this section for Kerberos authentication.
#<DirectoryMatch "^/QSYS\.LIB/PROFOUNDUI\.LIB/PUI000(3.{3})\.PGM">
# Require valid-user
# AuthType KERBEROS
# PasswdFile %%KERBEROS%%
# UserID %%CLIENT%%
# ProfileToken On
#</DirectoryMatch>

#<LocationMatch "^/profoundui/auth/(.*)">
# Require valid-user
# AuthType KERBEROS
# PasswdFile %%KERBEROS%%
# UserID %%CLIENT%%
# ProfileToken On
#</LocationMatch>

# Use this section for authentication against an LDAP directory with EIM mapping.
# This environment variable must be set to reference the path to the
# EIM configuration file for Profound UI.
# SetEnv PUI_EIM_CONFIG_FILE /www/profoundui/conf/eim-config.xml
#<DirectoryMatch "^/QSYS\.LIB/PROFOUNDUI\.LIB/PUI000(3.{3})\.PGM">
# LDAPConfigFile /www/profoundui/conf/ldap.prop
# PasswdFile %%LDAP%%
# AuthType Basic
# AuthName "Profound UI"
# Require valid-user
#</DirectoryMatch>

#<LocationMatch "^/profoundui/auth/(.*)">
# LDAPConfigFile /www/profoundui/conf/ldap.prop
# PasswdFile %%LDAP%%
# AuthType Basic
# AuthName "Profound UI"
# Require valid-user
#</LocationMatch>

# Use this section for authentication against a validation list.
# This environment variable must be set to reference the validation
# list object specified on the PasswdFile directive.
#SetEnv PUI_VLDL PROFOUNDUI/PUIVLDL
#<DirectoryMatch "^/QSYS\.LIB/PROFOUNDUI\.LIB/PUI000(3.{3})\.PGM">
# AuthType Basic
# AuthName "Profound UI"
# Require valid-user
# PasswdFile PROFOUNDUI/PUIVLDL
#</DirectoryMatch>

#<LocationMatch "^/profoundui/auth/(.*)">
# AuthType Basic
# AuthName "Profound UI"
# Require valid-user
# PasswdFile PROFOUNDUI/PUIVLDL
#</LocationMatch>

Are you certain that /IASP is set up in the IFS properly? For example, if you type the following at the command line, does it show the *PGM object?
If this fails (such as "object not found"), then perhaps /IASP isn't the proper path for your IASP...?

Yes, I´ve typed this command and it shows the *PGM objet PUI0005001.PGM

I don´t know if it´s necessary to modify other configuration parameters ...

Profound does not have a system with an IASP to test this with, but I know Profound UI works with an IASP because some of our customers are using it that way. I am certainly not an expert on IASP configuration (the customers who are using it have set it up that way themselves.)

From what I can tell, your configuration file looks good. But, like I said, I am no expert on IASP.

The error you provided means that Apache cannot file a file or directory. Here are some thoughts:

1) Maybe you moved the IFS directory into the IASP as well as the library? If you did this, then the directories beginning with /www will also need to be adjusted. (But, only if you moved the IFS directory)

2) Is it possible that the Apache HTTP server doesn't have access to the IASP? Maybe it needs to run SETASPGRP or similar? Or maybe it doesn't have authority?

These are just guesses, sorry.

Also be sure that you restarted the web server instance after making the config changes.

Scott, having the same issue, in the one of the last replies you state to use th SETASPGRP on the httpsvr, do you mean the profound http instance? If so how do we do this?

Scott,

The pui0001200 pgm is throw the error at statement 1362. What is that pointing to ?

The program has encountered an unmonitored exception. Please contact the system administrator for assistance.Message Id:PUI0005Severity:40Date:2015-01-29Time:17.06.58Program:PUI0001200Procedure:Initialize__FvLine(s):1362Message:Unable to start the application job.Cause . . . . . : The controller encountered an error while attempting to start the application job. The detailed error message is: 3025 - No such path or directory.

Recovery . . . : Contact the person responsible for program maintenance to determine the cause of the problem.

Unfortunately, we do not have an IASP to test the code with, so while the stuff listed in this thread "should" work to the best of our knowledge, it's also possible that there may be details that need to be fixed up.

Would you be willing to work with our team to work out the glitches? If so, please contact us at support@profoundlogic.com.