About Me

My photo
I work for Fusion5 Australia . Connect with me on linked in here . I'm raising money for a good cause at the moment, follow donate to leukemia foundation

Tuesday, 30 September 2008

All the AS/400 SQL you'll need for a ENT server rename

Note that this is AS/400 SQL syntax.

update svm7333/f98611 set omsrvr = 'NEWSERVER' where omsrvr =
'OLDSERVER'

31 rows updated in F98611 in SVM7333.

update svm7333/f98611 set omll = 'NEWSERVER' where omll =
'OLDSERVER'

31 rows updated in F98611 in SVM7333.

update svm7333/f98611 set omdatp = 'NEWSERVER - B7333 Server Map'
where omdatp = 'OLDSERVER - B7333 Server Map'

1 rows updated in F98611 in SVM7333.

update svm7333/f98611 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

1 rows updated in F98611 in SVM7333.
update svm7333/f986101 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

6 rows updated in F986101 in SVM7333.

SYS7333 F98611
update sys7333/f98611 set omdatp = 'NEWSERVER - Logic'
where omdatp = 'OLDSERVER - Logic'

1 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omdatb = 'NEWSERVER - B7333 Server Map '
where omdatb = 'OLDSERVER - B7333 Server Map '

3 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omsrvr = 'NEWSERVER' where omsrvr =
'OLDSERVER'

43 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omll = 'NEWSERVER' where omll =
'OLDSERVER'

44 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omdatp = 'NEWSERVER - B7333 Server Map'
where omdatp = 'OLDSERVER - B7333 Server Map'

1 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

1 rows updated in F98611 in SYS7333.
update sys7333/f986101 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

24 rows updated in F986101 in SYS7333.

update sys7333/f986101 set omdatp = 'NEWSERVER - Logic'
where omdatp = 'OLDSERVER - Logic'

11 rows updated in F986101 in SYS7333.
update sys7333/f9650 set mmmkey = 'NEWSERVER' where mmmkey = 'OLDSERVER'

1 rows updated in F9650 in SYS7333.

update sys7333/f9650 set mmdatp = 'NEWSERVER - B7333 Server Map'
where mmdatp = 'OLDSERVER - B7333 Server Map'

1 rows updated in F9650 in SYS7333.

update sys7333/f9651 set mdmkey = 'NEWSERVER' where mdmkey =
'OLDSERVER'

5 rows updated in F9651 in SYS7333.

Make sure EDRSQL TCP service is running "STRTCPSVR SERVER(*EDRSQL)". Make sure that it starts automatically (use iSeries nav for this)

AS/400 issues

I like AS/400 issues... Why, because there are always so many logs... I really love job logs... As far as an OS is concerned, does logging get any better? Event viewer is good, but not great. stdin and stdout is okay, but job logs... They boil my potato!

I was configuring a DR AS/400 today and was getting a really strange error "Cannot resolve to object QBFCPRCED". When we looked for that object on the DR machine, it did not exist... YET, when I looked at the object on the prod machine it did... what does that tell you? Not a good start to a DR machine it tells me. How do people expect this thing to work without the correct foundation... Anyways... Despite this, there were a bunch of PTF's that were installed but not applied. We IPL'd the 400 (30 mins later, brand new 520!) to install the PTFs - Bob's your uncle and fanny is your aunt (I said aunt) She started working!

Remember if you want to build up an ent server (or change the name), you gotta do the following:
JDE.INI on the server - old to new
update SY and SVM F98611 and F986101
Update F9650 and F9651
Update client ini files

All of the fat client ODBC's needed to be changed, export the ODBC part of the reg and do a search and replace - much easier.

Remember that the web servers (despite maybe having a fat client), do not use ODBC - all JDBC. These are loaded up on the fly from F98611 - so you don't gotta worry about them.

Tuesday, 23 September 2008

WebDev client for OAS

Remember that if the web dev is not working, you can go to the deployment server under OneWorld Client install\WebDevFeature and run the installer from there. You'll know if it's working because it'll finish (ironic!). If the installer does not finish, reinstall your fatty and then run that again.

JDE and LDAP

It's not the best implementation of LDAP authentication I've come across... But, lets have a more honest look at things, is it the worst... Hmmm, it might be.

What about some of the limitations:

1 domain only
username < 10 chars
password < 10 chars WTF!!!! This is a crock!

okay, and now the best stuff...

So I work as a site with a large AD implementation, 5000 users... something like that... Not that many JDe users... Each time a user tries to login to JDE, the security kernel is saying "Cannot find username XXXX in LDAP"... But, any LDAP browser or MAD tool can. I don't know how it's running it's queries, or if it's binding to the correct member - but it's bad!

Tuesday, 16 September 2008

If you can't get into the em console, try this

D:\product\10.1.3.1\OracleAS_1\opmn\bin>opmnctl startproc process-type=home application=ascontrol
opmnctl: starting opmn managed processes...

then http to:
http://machinename.domain.etc/em/console/ias/cluster/topology

opmnctl usage

usage: opmnctl [verbose] [] []

verbose: print detailed execution message if available

Permitted // combinations are:

scope command options
------- --------- ---------
start - Start opmn
startall - Start opmn & all managed processes
stopall - Stop opmn & all managed processes
shutdown - Shutdown opmn & all managed processes
[] startproc [= ..] - Start opmn managed processes
[] restartproc [= ..] - Restart opmn managed processes
[] stopproc [= ..] - Stop opmn managed processes
[] reload - Trigger opmn to reread opmn.xml
[] status [] - Get managed process status
[] dmsdump [=&..] - Get DMS stats
[] set [= ..] - Set opmn log parameters
[] query [=] - Query opmn log parameters
ping [] - Ping local opmn
validate [] - Validate the given xml file
config [] - Modify the opmn xml file
help - Print brief usage description
usage [] - Print detailed usage description

Clustering in OAS

Make sure that you name your OAS instances (when doing the initial install through the oracle installer 0 YUK!!) differently. They need to have different names for the cluster to work. Thansk Rhys.

OAS timeout

ISSUE:
Customer is running a JAS server using OAS and needs to find out how to set the time out settings.
From an HTML client, the system times out within 15 minutes.


SOLUTION:
Oracle AS Session timeout is by default set to 20 minutes. To set higher timeout, please follow the steps as described below.

FOR OAS 10.1.3:
1. Select your OC4J container
2. Click on "Application" Link
3. Click on link for your E1 JAS OC4J, eg "EA_JS_81"
4. Click on the link for webmodule, "webclient"
5. Click on link for "Administration"
6. Under "Go to Task" column, click on icon for "Configuration Properties"
7. Set the Session timeout value in Seconds
8. Restart the OC4J instance


FOR OAS 10.1.2.0.2

1.) Update the WEB.XML

a.) Navigate to JAS Application under /j2ee//applications/jasapp/webclient/WEB-INF
b.) Make sure that server is not running.
c.) Edit the WEB.XML file using Notepad.
d.) Place the 3-line session-timeout stanza in the WEB.XML file like this:
...

MOViewerServlet
MOViewerServlet
com.peoplesoft.e1.container.MafletServiceContainer

maflet.name
MOViewerServlet




30


Where the number entered for "session-timeout" is the desired session timeout in minutes.


2.) Update Apache:

a.) Find the httpd.conf file located in /Apache/Apache/conf
b.) In the httpd.conf file, change the "Timeout" value.

Timeout 300

This value is in seconds and is set to a default of 5 minutes (300 seconds) and should be changed to match your desired timeout. (e.g. 1800 for 30 minutes, 3600 for 1 hour).


3.) Update the MOD_oc4j.CONF (located in ORACLE_HOME>/Apache/Apache/conf)


a.) To update this file, refer to the document using link:
http://download-west.oracle.com/docs/cd/B14099_07/web.1012/b14007/confmods.htm#CIHJCHHH

You will need to add/change the value for "Oc4jConnTimeout" to be that of the time (in seconds) before the connection timeout occurs (e.g. 1800 for 30 minutes, 3600 for 1 hour).


4.) Update the UserSession value in the relevant JAS.INI (located here: /j2ee//applications/jasapp/webclient/WEB-INF/classes)
to match the timeout set in the other three steps listed above. The JAS.INI value will need to be entered as milliseconds (e.g. 1800000 for 30 minutes, 3600000 for 1 hour).

The JAS.INI setting for timeout is as follows:
[CACHE]
# These intervals are in milliseconds. For example, 60000ms = 1 minute, 3600000ms= 1 hour
UserSession=3600000 <====

Working with steps 1 and 4 above should suffice. However, it may be necessary to also complete above steps 2 and 3 should you not see your changes enforce your desired timeout setting. Also, note that this is a crucial timeout value. Setting your timeout higher than 30 minutes may cause higher memory usage and out of memory conditions. Please take care in using this setting as performance may be affected adversely.

Monday, 15 September 2008

F00928 - LDAP config

Remember that this is where your LDAP info is set. Out of the box this is in the data owner. It gets worse too... The default environment in the JDE.INI [SECURITY] (not too sure if this is the correct stanza, there is only two) is looked at to find which F00928 is going to be looked at...

I generally map all of these to SYSTEM and keep one copy!

Thursday, 11 September 2008

second fact about tools release update package

Oh yeah, I remember the second item now...

Secondly if you create an update package that is for the new system only, compress the new system. It'll update the pacakge_inf file for the parent package as well as the one you just built. This was a little unexpected and so are the results, anyone who takes the full package you built the update against will get the new tools release! The following line is updated in the fullpacakge.inf file:

SSYS=\\NSGSHSJDNDPLY01\E812\897.2.1\systemcomp

Where build location is defined as "NSGSHSJDNDPLY01" and foundation path defined as "\E812\897.2.1\system". This is from the foundation item revisions screen (P9883).

WAS6 & 8.97.21

Here is a couple of basic tips.
New tools release update package:
When you define a new system, so that you can build an update package that will throw out a new tools release, and not affect the other clients... So you create a new system, and it asks you for a directory... You gotta use a unc share to the dir, and you need to select the system DIR, not the systemcomp DIR...

There was going to be something else, but I forget.

Tuesday, 9 September 2008

What do I do with 8.97 and server manager

Don't know where to start?

This is a late post, but it takes time to get my head around things.

Download the following (server manager for the tools release you want to install) from www.peoplesoft.com, or use change assistant. Change assistant is great, if you are not using it, you should start.

Remember that the par files are zip files, peoplesoft archive, what a crock! they should be oar files anyway.

There is no birds eye description of what you need for this 8.97 stuff, so I'll try and write a simple one.

  • You need to install the "server manager" on a machine somewhere, deployment server makes sense. This machine needs a lot of disk.
  • The server manager is NOT the client software, it's just another GB that you need to download
  • All of your other servers need agents installed, each agent can be downloaded from the software management pages (which you are going to install on your deployment server). Generally a link like "http://deploymentserver:8999/manage"
  • This is one reason the download is so big, it contains all of the agents!
  • you then need to download the client (another GB), and all of your other server types.
  • The server manager co-ordinates the installation and configuration of all machines in your 8.97 installation, it's important
  • You don't get direct access to SAW anymore, this SUCKS!
That is the download, now the install. you should have at least 4 par files. One for your web server, one for your enterprise server, one for the client and one for the server manager.

We install the server manager first.

Note:
  • If this is a new install, don't blaze ahead and expand the par files and install the enterprise server and the web servers... Server manager does this for you!!!!!
  • It does not have to install the base product, but it's damn good at it.
  • If it's an existing install, install the agents. They talk back to the server manager and tell it what is going on.
  • If you are installing websphere, you still need to install WAS. Note that if you are using WAS6.0.2.21 (not 6.1) you'll not be able to find the jar files that allow remote management of WAS (This is a nightmare). I had to download the client for 6.1 to get the jar files
  • com.ibm.ws.admin.client_6.1.0.jar (31 Mb)
  • com.ibm.ws.security.crypto_6.1.0.jar (12KB)
  • ibmkeycert.jar (209KB)
  • you go to http://nsgshsjdndply01.xxx.xxx.local:8999/manage/wasadmin to upload the files
run the smmc_setup.exe from the disk1 sub folder. choose a folder with some space, enter a password, accept the default port. Install the 780Mb!!

This creates a service called "SM Management Console".

It'll create a readme.txt file in the root dir of the install (D:\jde_home). this has the URL that you need (in case you've forgotten).

# Oracle JD Edwards|EnterpriseOne
# Server Manager
# Management Console
#
Installation location: D:\jde_home
Installation log files are in: D:\jde_home\logs folder.
Management console URL: http://nsgshsjdndply01.xxx.xxx.local:8999/manage

When you log in for the first time, you'll need to go through a wizard.






Wow, that's painful putting a picture in, especially one as unhelpful as that!

So, my screen is now frozen on the wizard... Click next, nothing happens... Awesome. This is using IE6 from the deployment server. I also added the site as a trusted site, nothing! Lets try Mozilla, or maybe my new fav. Chrome. Get in there!

Well, it works from Mozilla on my client... Lets move on.

I used the default JMX ports etc, 14501 et al

enter the system data source info.

bcoz I'm working at an oracle site at the moment, I need to paste in a decent tnsnames.ora file. I get it from (C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN).

Enter you database username and password

Now you get the option to import the JDE users from F0092 (how smart is this thing??)

Now it tells me:

Please refer to the documentation for additional steps that are typically performed after the initial installation. These may include the following tasks:

  • Configure Server Groups
    Server groups are used to logically separate similarly purposed servers. For example you may create one server group that contains the development servers and another group that contains the production servers.
  • Configure Management Users
    You may create user groups to logically associate user names with their activity role. By granting the user groups individual permissions you control what task and activities users may perform within the management console.
  • Install and Register Servers
    Once the desired server groups are created and configured you may use Server Manager to register your existing enterprise servers and application servers or perform new installations of enterprise servers and the web-based EnterpriseOne servers.
Ready to rock. From my new machines, AP server and WB server. I'll access the URL for server manager and download the appropriate agents.

Add servers to console

You may be wondering (like I did) how the f*%k can I add my other servers... Be patient. Install the agents and they will appear. Remember that 8999 is the port for the agent installs, not the JMX ports. Goto the management agents left menu item and then click your OS type.

They need to get valid publisher information for these installs, it looks much more professional.

After you've installed you agents, hit F5 on the main screen, and ka-boom, new servers appear!
http://nsgshsjdndply01.xxx.xxx.local:8999/manage/home

Okay, so now I've got 3 machines listed. that's it. The good news is you hardly need to access the servers via RDP anymore, the agent is going to do everything for you.

Get software to managed nodes
Now we have to upload some software into the server manager so that we can distribute it to the agents.

Goto managed software and "upload file", alternatively you can just copy your par files into the "D:\jde_home\components" dir on the deployment server (where you installed the server manager, I'm going to call it the DEP server from now on).

If you copy the files in, they will appear in the list with a refresh (or two). Might need to restart the SM service if you are waiting too long (like me). Note that this did not work for me either - WTF! So, I've copied the files in, but only one has been recognised. I'll try and tell it to upload from the components dir (I think that I've done this before and it roots everything up).

Ahh, I know. It does not pick up the client par or the WSG pars. bit crap if you ask me. Should list them but allow you to do nothing with them.

Please also note that although the service control panel comes back to you quickly, you'll need to wait longer to sign into the admin console.

Install WAS instance

Add server1 as some managed software


install your jdbc drivers.

To install a JDE web instance, you gotta install a J2EE container first.

choose your webserver
choose server1
choose your profile name (default)

add a server, choose a name like "AS_JS_81SP" and okay

now create a enterpriseOne HTML server

WAS will confirm the webserver name (for mappings)

WAS will ask for basic environment information.

create, then you gotta configure the INI and the JDBJ with the SM interface (yuck).

Goto the link "JDBJ Database config" and fix all of the settings

Wow, when you install a WAS6 instance of JDE, it creates all of the httpd.conf information in an include file and writes the directives to the httpd.conf. That is cool.

include "D:\IBMHTTPServer\conf\scf_AS_JS_81SP.conf"

Enterprise Server:

After adding a new server, the system dir is there, but no pathcodes. I guess I might have to read the guide to work this out - although it's not stopping me having a go!