in the [OWWEB] section of the JAS.INI there is a setting:
I think that 126.96.36.199 the default might be false.
To tell you the truth, I did not know that…
With tools release 8.97 and higher it is no longer necessary to use the MO QUEUE folder path in the jas.ini, which was required in previous releases. The configuration now comes from the web.xml file and is automatically configured. As for the port and share settings, they are now incorporated in Server Manager. To access these settings:
Note: After making any permission changes, be sure to stop/start services for server manager and then restart the jas instance using server manager.
By default, media objects are stored on the deployment server running a Windows operating system. Unless the Unix, Linux, or AS400 server hosting the HTML Web Server is able to map a network drive to the deployment server with read/write authority, FTP protocol should be used to store and retrieve media objects.
To prepare an FTP Server for Media Objects:
Follow the instructions below to add the FTP Server component to the deployment server. These instructions are based on the Windows operating system but may change as Microsoft has new releases. However, the steps will be similar.
Follow the instruction below to set up a Media Object directory on the FTP server
Note: When setting up the FTP, make sure the path goes to the installed E1 directory such as c:\900 and not directly to the media object queue folder.
To configure the E1 HTML Web Server to use FTP for Media Object storage and retrieval, go back to the jas.ini or server manager and configure the [OWWEB] or Web Runtime section with the correct Port and login information.
To test your FTP site:
On your HTML Web Server, use an FTP client and manually connect to your deployment server using the information specified in the jas.ini. Change the current directory to B7333, B7334, B9, E810, E811, E812, or E900. Test putting and getting a file to and from the server.
Note: As mentioned previously, use the UPN naming convention for the Queue Path in P98MOQUE. For instance, if your deployment server for E900 is DEPSRV, your queue path should begin with \\DEPSRV\E900. To use this queue path, the HTML Web Server connects to DEPSRV using FTP on the port number specified in the jas.ini, and logs on using username/password also specified in the jas.ini. Then the HTML Web Server tries to change the current directory to E900. The E900 virtual directory must be available under the Default FTP Site.
Where do I start…
You definitely cannot install the H4A61_setup.exe if you have WAS6.0 locally. Note that you will not get any error messages or anything, it’ll just fail.
You can go to the WASHOME\bin dir and run command “versionInfo.bat” file and it will tell you the exact version of the local WAS express product.
Then run the associated install pgm from \\DEPSERVER\E812\OneWorld Client Install\ThirdParty\WebDevFeature\ dir.
Note that you can do this at anytime and the correct webdev feature will be installed, even if u did not include it in the package build.
There are some command line options for the InstallShield program to help u too:
H4A61_setup.exe -is:javaconsole -is:log c:\temp\install.log
Also change your TEMP and TMP env variables to something a little shorter
Also, there is a know issue where the WAS6 does not get uninstalled properly before installing WAS61, which will ensure that nothing will ever work again.
See this for instructions for manually removing WAS6: uninstalling Websphere Express 6.0
All reports (package build etc) from all environments produced blanks… At least it was a couple of pages of blanks, and it had the underlines too – helpful. Problem was, I could not fill in all of the blanks… No matter how good my imagination was.
This turned out to me missing resource dir from the deployment server system dir. None at all!
I copied it in from a new 8.98 fatty and all is good now.
Okay, so now I have a real problem.
Server Manager makes a lot of things easy, but makes a lot of things hard at the same time. It takes away that level of control that you sometimes need.
For example, I use the transaction server for RTEs out of E1. Previously I created an additional profile (non federated) for my RTE functionality. This was my preference to keep it all separate. It all worked well back in 188.8.131.52… But I try to use SM for the install in 184.108.40.206 and it was a webserver!! What, I don’t need a webserver…
So now I have to follow complicated instructions here http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp for creating a web server for a non default profile, or maybe just create the RTE in the default profile (which I think that I will do).
Wow, what a time I’m having with an AIX 8.98 installation. I’m going for 220.127.116.11, and have had issues. I believe that if I was following instructions, they would tell me… You need to run the E812ToolsEnvSetup.sh from your $SYSTEM\bin32 dir so that all of the libraries can be found. I was manually hacking into the .oneworld – which is not the solution.
Note another little thing that needed to be done. When introducing SM to all of my servers, I needed to add the network deployment manager so that all of my network deployed applications could be seen. This took a tres long time, but the results are worth it. I have this complete remote management ability in SM – v cool.