Testing JSP Changes In IBM WebSphere Without ReStarting The Service

This is a follow-up to my previous post “Restricting The EnterpriseOne Evironment On The JAS Server”.

While coming up with my solution to how to restrict users to an environment when logging on to a JAS server that hosted a path code with multiple environments attached to it, I wanted to be able to test my changes “on-the-fly”.  I didn’t want to restart the service every time.

So, that’s when I found the “temp” directory.

• This is the “production” directory:
  C:\WebSphere\AppServer\profiles\default\installedApps\Node01Cell\JPD811_HTML.ear\webclient.war\share
• This is the “temp” directory:
  C:\WebSphere\AppServer\profiles\default\temp\Node01\JPD811_84\JPD811_HTML\webclient.war\share

A file named “_html4env.class” will be placed in there when a user logs in.  It is a compiled version of the “html4env.jsp” file.  So, if you delete that file and make a change to the “html4env.jsp” file or the “_EnvRestriction.htm” file, when a user tries to login WebSphere will compile the “html4env.jsp” file and create a new “_html4env.class” file with your changes.

Tags: E1Tips, enterpriseone, EnterpriseOne - General, EnterpriseOne - JAS (Java Application Server), Java, Java Application Server (JAS), JVM, oracle, websphere

Windows Vista / Windows 7 & IBM iSeries IFS Mapped Drive

If you are using Windows Vista or Windows 7 and need to map a drive to an iSeries IFS directory you will need to follow the steps below:

1. Open the Local Security Policy editor: Start – Run – “secpopl.msc” – Ok
   
2. If a User Account Control window appears, click [Continue].
3. Expand Local Policies – Security Options
   
4. Double-click  “Network security: LAN Manager authentication level”
5. Change the value to “Send LM & NTLM – use NTLMv2 session security if negotiated”
   

 

 

This is documented on IBM’s website: http://www-01.ibm.com/support/docview.wss?uid=nas2bb4cf3cc6d1a859e862573900041ed36.

Another install-related issue concerns installing from the     
applied System i PTF.  Once the PTF is applied, you can install
this service pack or complete merged image from the network   
share called QIBM on your System i.  Accessing this share uses 
the LAN Manager component of Windows, and NetServer support   
on the System i.  In Windows Vista, Microsoft has changed the 
default negotiation method for such connections, so that, at   
this time, accessing shares on the System i may fail. One way 
to work around this problem is to change a policy setting on   
the PC.  This action requires administrator authority, and can 
be performed as follows:                                       
  1) Click Start, click All Programs, click Accessories, click 
     Run; then type "secpol.msc" (without the quotes) in the   
     Open text box, and click OK.                             
  2) If a User Account Control dialog box appears. verify that 
     the details shown match the request you initiated (you are
     starting the Microsoft Management Console), and if so,   
     click Continue.                                           
  3) From the Local Security Settings console tree, expand     
     Local Policies, then click Security Options.             
  4) In the right pane, scroll down to the setting called     
     "Network security: LAN Manager authentication level       
     Properties" and double-click it.                         
  5) Note the current value.  The default value at the time of 
     this writing is "Send NTLMv2 response only".  If the value
     is not as follows, change it to be:                       
     "Send LM & NTLM-use NTLMv2 session security if negotiated"
     then click OK, and exit the Local Security Settings       
     console. You should now be able to access network shares 
     on the System i.                                         
The last issue related to install has to do with installing   
from a network share.  Testing has shown that, in some cases, 
installing System i Access for Windows on a Windows Vista PC   
from a network share fails.  In such cases, copying the files 
from the network share to the PC’s local hard disk, then       
re-starting the installation from the local hard disk,         
completes successfully.                                       
Alternatively, you can map a drive to the network share in a   
Command Prompt box that was opened as administrator and start 
the installation from the mapped drive.                       
To open a Command Prompt box as administrator, click Start,   
then All Programs then Accessories, right-click the Command   
Prompt icon and choose Run as administrator. This action will 
prompt you to allow the Command Prompt program to run elevated.
At the Command Prompt, type in the following command to map the
network drive:                                                 
  net use X: \\server_name\share_name                         
where X: is the drive you want to map, server_name is the     
network server’s name and share_name is the name of the shared 
directory. If you are installing from a System i, you would   
type in                                                       
  net use X: \\system_i_name\QIBM                             
Then change to the mapped drive in your Command Prompt box and 
run the setup program from there. If you are mapping a drive   
to the QIBM share of your System i, these are the steps you   
should follow for a 32-bit installation of System i Access     
for Windows V6R1:                                             
  X:                                                           
  cd ProdData\Access\Windows\Image32                           
  setup.exe                                                   
If you are installing on AMD64 or on Itanium hardware use     
Image64a or Image64i instead.                                 
The cause of this failure is being investigated.

Tags: enterpriseone, EnterpriseOne - General, IBM i/System i/iSeries/AS400, IFS

Create A Windows Service / Delete A Windows Service (sc create / sc delete)

Today, I came across a Windows Service on a server that I inherited. By the name of the service I could tell that it was built in-house and I even found enough information to determine who the developed it.  However, since it was not in the Add / Remove Programs list of the Control Panel, I wasn’t sure how to remove it.  So, I found the following on Geeks With Blogs – Shahed’s Blog:

Recently, I was trying to delete a windows service. Normally it should not be necessary to manually delete a service. Uninstalling an application should remove its associated service (if any).

However, I installed some beta products and a service created by one of the applications was not removed automatically. Its very easy to remove a service from registry if you know the right path. Here is how I did that:

1. Run Regedit or Regedt32

2. Find the registry entry "HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services"

3. Look for the service there and delete it. You can look at the keys to know what files the service was using and delete them as well (if necessary).

alternatively, you can also use command prompt and delete a service using following command:

sc delete < SERVICE name>
or to create, simply type
sc create <SERVICE name>

Update:
If you have space in the file path you need to use quotation marks ("). For example: 
sc create "MySQL" binpath= "C:\Archivos de programa\MySQL\MySQL Server 5.1\bin\mysqld.exe"

I used the “sc delete” method to remove the service.

Thanks, Shahed!

Tags: enterpriseone, EnterpriseOne - General, Microsoft, RegEdit, Windows Server

How To Build A SRVPGM Using The Command Line

The other day we had an issue with building a full package for one of our EnterpriseOne installations.  The issue was related to not having the same tools release active on both the Deployment Server and the Enterprise Server.

However, I found something rather interesting.  You can build an individual package DLL or SRVPGM on the System i (AS400, iSeries, i) using the command line. 

According to Oracle Support Doc ID 630044.1 you could use the CRTCMOD command.  However, this may error because “any object that has a #include for jde.h will not be found”.

The correct steps you must use to compile a DLL or SRVPGM using the command line is below:

1. Add the EnterpriseOne system library using the following:
   

   addlible e811sys

2. If you wished to build the CFIN SRVPGM, run the following command:
   

   call builddll '/oneworld/packages/<packagename>/text/cfin.txt'

Hopefully, this will help you if you ever need to build a DLL or SVRPGM using the command line.

Tags: *SVRPGM, enterpriseone, EnterpriseOne - General, IBM i/System i/iSeries/AS400, Tools Release

Journaling a Physical File on IBM iSeries Using STRJRNPF

We have a system that needs to interface directly with some EnterpriseOne Files.  This system is written in Java and seems to be very difficult to change any JDBC settings to not use commitment control.

Anyway, to get around this issue, we started journaling the physical file that the JDBC command was trying to update using the following command:

STRJRNPF FILE(PRODDTA/F0911) JRN(OWJRNL/OW_JRNL)

Tags: enterpriseone, enterpriseone, EnterpriseOne - General, ibm, IBM i/System i/iSeries/AS400, iseries, Java, JDBC, JDBC, JDBJ, system i

Server Management Will Not Start After Update

We are updating our EnterpriseOne Tools Release to 8.98.2.2 and had an issue with updating the Server Manager Agent on our Windows web servers. After following the steps to do the update of the Server Manager Agent it would not restart. I was able to find a document (Doc ID 983043.1) on Oracle Support that fixed the issue.

To resolve this issue, Customers need to download the 8.98.2.2 (or newer) version of the Server Manager update component and proceed with the following steps:

Update your Server Manager console with the newer version of Server Manager.

Locate the “scfagent.jar” file in the following directory:
{jde_home}\targets\oc4j\j2ee\home\applications\ManagementConsole\ManagementConsole_WAR\scfagent
where {jde_home} is your Server Manager console install location.

Copy this file to the following directory on the machine where your Windows Server Manager agent is running:
{jde_agent_home}\lib\_staging
where {jde_agent_home is the Server Manager agent install location

Rename the “scfagent.jar” file that you have copied to “agentUpdate.jar”. If there is already a file with this name, it should be replaced with the new file you have copied.

Run the “startAgent.bat” command file twice from the {jde_agent_home}\bin directory. The first time will update the Server Manager agent JAR files with the newer version, but will likely fail to start the service. The second time should start the service successfully.

I hope that helps!

Tags: enterpriseone, enterpriseone, EnterpriseOne - General, EnterpriseOne - JAS (Java Application Server), jde, oracle, Oracle Server Manager, Server Manager, Server Manager, Tools Release, version, xe

Web Only Version Pain

We seem to be having an issue with old “web only” versions.  There are times when the “web only” version causes the other version to not egen correctly.  So, below is the SQL that can be used to select the “web only” versions.

SELECT count(*) FROM COPD811/F983051
WHERE VRVCC2='1'             

If you want to be more precise, you can grab the “web only” versions that have been executed prior to a certain date by using the VRVED field and the six digit date which can be found on the e1 dates page.

Tags: e1, eGen, eGen, EnterpriseOne - General, EnterpriseOne - SQLs, sql, sql, version, versions, xe

How To Find EnterpriseOne Web Only Versions

Dealing with EnterpriseOne “Web Only” versions can be a real pain.

They are deleted with each full package deployment and can cause a lot of confusion for the users.

In order to find these troublesome quasi-objects you can run the sql below:

Tags: Batch Versions, eGen, enterpriseone, enterpriseone, EnterpriseOne - General, EnterpriseOne - SQLs, fusion, sql, version, versions

EnterpriseOne Event Rules Debugger Broker Error

The other day I was notified by a developer that he was receiving the errors pictured to the left when opening the debugger.  The application looked like it opened just fine and then right before it was done, these errors would appear.

 

I checked all the logs and re-installed the BPM Broker but the error persisted. 

Then I searched the My Oracle Support site and… tada!  A hit.  Knowledge Base ID 661700.1 had the solution.

There are about 5 different solutions listed and, of course, my issue was resolve with solution #5.

1. For 8.97 and higher Tools Releases Only:Make sure the following DLL files are registered on the workstation using the command

regsvr32 <Drive Letter>:\<E1 Release>\system\bin32\<DLL name>

E1Soap.dll
DebuggerService.dll
WinUBEDbgService.dll
JDEBPMSoap.dll
JDEBPMSockets.dll

I’m not sure which DLL was having the issue, but after I ran through these commands the error went away.

Hope this helped. 

 

 

 

 

 

 

 

 

 

Tags: BPM Broker, e1, E1Tips, enterpriseone, EnterpriseOne - General, jde, oracle, Tools Release, ube

Batch Version (P98305W) Version Error

After our latest tools release update there was a special instruction that I forgot to do on one of the environments.  It was to delete all versions of the Batch Versions (P98305W) application.  Usually, there will be just one version: ZJDE0001.

Well, since I forgot, to the left is the error that you might get if you don�t do it.  The second image is the Interactive Versions screen that you will need to use to delete the version.

Tags: batch version, e1, enterpriseone, EnterpriseOne - General, EnterpriseOne - Install/Upgrade, jde, Tools Release, Tools Release, version, versions

Next Page »