using WAS on your 400–httpd.conf config for E1

If you are installed JAS on your 400, remember that you need to follow the instructions on the screen.  If it says “follow what is in the readme.txt”, things are not going to work unless you do it.

Please perform the following manual steps.
------------------------------------------

1. Add the following text to the Managed Instance's associated HTTP Server's httpd.conf file.
------------------------------------------------------------------------------------

# The following configuration was added by the EnterpriseOne Server Configuration Framework

Listen 0.0.0.0:9085
<VirtualHost *:9085>
Alias /jde "/QIBM/UserData/WebSphere/AppServer/V7/ND/profiles/default/installedApps/HDRYDOW/WAS7_DV_85.ear/webclient.war"
</VirtualHost>
<Directory "/QIBM/UserData/WebSphere/AppServer/V7/ND/profiles/default/installedApps/HDRYDOW/WAS7_DV_85.ear/webclient.war/WEB_INF">
Order Deny,Allow
Deny from All
</Directory>
<Directory "/QIBM/UserData/WebSphere/AppServer/V7/ND/profiles/default/installedApps/HDRYDOW/WAS7_DV_85.ear/webclient.war">
Order Deny,Allow
Allow from All
</Directory>
------------------------------------------------------------------------------------

2. Restart the Managed Instance's associated HTTP Server to pick up the changes.

ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ALL)

STRTCPSVR SERVER(*HTTP) HTTPSVR(*ALL)

Extra note for AS/400 monitoring

Changes to management central configuration (i.e. when we ask it to automatically restart failed monitors) only take affect once the management central services are restarted:

This can be done with:

1. In iSeries™ Navigator, expand My connections > System A > Network > Servers > TCP/IP.
2. Right-click Management Central and select Stop. Wait until the Management Central server has stopped. Press F5 to refresh the screen and view the status in the right pane. The status should display Stopped when the server has stopped.
3. Right-click Management Central and select Start. This will restart the Management Central servers on the Central System.
4. Repeat steps 1-3 on the target systems: System B, System C, and System D.

Note that it’s a TCP/IP server, so you can do it with STRTCPSVR *MGTC

Note that this was a helpful article too http://www.mcpressonline.com/system-administration/general/automatically-restart-failed-monitors.html

I did not do this in anger, but assume that it’s not going to affect anything.  I’d probably do it after hours the first time, just to be sure.

This shows that because TCPIP is ended for the backup, this is the reason that the management service is restarted when TCP is:

 

proactive AS400 monitoring–out of the box

I have a client that wants to do some more pro-active monitoring of their AS/400.  They want to know if something has failed before their users tell them – innovative!  Different!  Forward thinking!  Let’s be honest, if you read the doco, there are never any problems on an AS400 and this is a waste of time – but maybe not!

I did a little bit a research and I’m amazed what is available “out of the box”.  With some smarts about what to do and how JDE works on the AS/400 – monitoring is fairly easy.

There are 5 main categories of monitoring:

These are available from your “Management Central” location within the system I navigator.

What are you going to monitor, here is a start:

• Disk usage
• CPU usage
• Errors in certain job logs (wow, this is GREAT) [tell me if I get
• Errors in QHST log file, errors in any log file
• Message in queues

All very possible given the above frame work.  You can just right click and start adding them.  We have our AS400 sending emails when certain disk, CPU thresholds are met.  We have it sending emails when backups are complete and also if there are certain messages in QHST (

SYSTEM

Note that I look at what is available (with Graph history), and then add monitors for things that I want to monitor

FILE

You can use a file monitor to notify you whenever a selected file has changed,reached a specified size, or for specified text strings.

QHST for any system problems (CPF1124 – Job start)

JDE log files for specific messages / text strings

JOB

Check jobs for certain messages in job logs

Check existence of jobs, CPU usage of job, count of jobs, thread count etc.

If a UBE is killing the system, you could actually give it lower priority – this is POWERFUL!

You could move a job out of a queue if it was taking too long, this is VERY powerful (with the use of replacement variables)

Message

Monitor for messages in a single message queue.

 

If your monitors are not auto starting

Restarting failed monitoring on the 400

you can manually select the option for “Restart on failed systems” – but this is a pain.  Fix the problem permanently!

Then choose “Connection”

 

In my research found the following helpful:

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzahx%2Frzahxmonparent.htm

System iSystems Management Working with Management Central monitors Version 5 Release 4

This was also a VERY good presentation http://www.lisug.org/presentations/Monitoring%20System%20Performance%20Sept2012.pdf

Pop quiz

If you are on an AS/400 and want to secure and directory or library from a particular user that has *ALLOBJ authority, can you do it?

….

You have a 50/50 chance on this one.

…

The correct answer - NO

http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/index.jsp?topic=/rzarl/rzarlallobjsa.htm

*ALLOBJ special authority

All-object (*ALLOBJ) special authority allows the user to access any resource on the system whether private authority exists for the user.

Even if the user has *EXCLUDE authority to an object, *ALLOBJ special authority still allows the user to access the object.

Risks: *ALLOBJ special authority gives the user extensive authority over all resources on the system. The user can view, change, or delete any object. The user can also grant to other users the authority to use objects.

A user with *ALLOBJ authority cannot directly perform operations that require another special authority. For example, *ALLOBJ special authority does not allow a user to create another user profile, because creating user profiles requires *SECADM special authority. However, a user with *ALLOBJ special authority can submit a batch job to run using a profile that has the needed special authority. Giving *ALLOBJ special authority essentially gives a user access to all functions on the system.

 

Let me know if you got that right!

iSeries work station definitions–prompting options

Want to default a particular login option for all users on your terminal server for client access and do not know how – well I do.  A great start was found here, but alas the finish was not that great!

http://forums.citrix.com/thread.jspa?threadID=62545

They said to change the user id field in the .cae field, but this is not right.

You will have a .cae file for all of the .ws definitions that you have.  You’ll want to modify the one that your users use. 

[CAE]
UserIDSource=0
UserID=

It’ll look something like the above.

Note that the userIdSource is basically an array, with 0 being “Use windows username” and 3 being “User Kerberos”

Change the UserIdSource to be the array value that you want, – 2 in my case for prompt ever time

Seems to have done the trick.

Oracle–the complete solution

The complete oracle solution is a complete reality, and a strategic direction that is very appealing for the JDE centric organisations.  Firstly, what do you need to run JDE?

• Hardware
• Storage
• Virtualisation
• Operating system
• Database
• Web Servers
• Application
• Management

How can oracle help with all of these requirements, it’s now fairly easy.

Hardware, as you know is going to be x86 or sprac, there are no limits to the performance and scalability that oracle can offer you in this area.  Exadata and Exalogic will give you the ability to crush ANY processing requirements that you might have.  Throw generic x86 processing at the problem, simple and cheap and able to run oracle standard edition.  If you can afford enterprise edition database, then other engineered solutions, like an ODA, might suite your requirements.

Storage.  Many of the engineered solutions have storage built into them, whether it’s ODA or exalogic or exadata.  Bigdata is going to solve all of your big data problems.  Oracle also have a range of SAN based technology to sort your larger storage requirements – the pillar axiom 600 could help you here.

Virtualisation is simple and Oracle Virtual Machine can create a highly available resilient solution for your enterprise.  You can be fully supported and take advantage of machine templates from Oracle, so save time and money and force you down the path of best practice.

Operating Systems – look no further than Oracle Enterprise Linux.  If you need a supported linux OS for your oracle requirements (or any requirements), look no further.

Database – one word – Oracle.  More words, scalable, performance, reliability.  It’s no longer  a difficult or expensive database.  Conceptually people think that it’s oracle and it’s difficult and expensive, we have clients that do not touch their x85 based oracle database for a year and it just runs…  Enterprise Manager allows you to manage the database through a simple and graphical method.

Web Servers – WebLogic is the best web server available, it’s that simple.  Template are easy.  It’s fast and stable.

Application – JDEdwards

Management – This is like the icing on the cake.  Everything I’ve mentioned can be managed with a single management solution.  Raise cases, alert you if something is wrong.  Manage your entire stack with a single management solution.  The technology is simple, you just need to manage it!

SOAP connector address in WebSphere & updating webmethods JDE integration server

finding your soap port for websphere (used for connecting SIB explorer)

find serverindex.xml, in a dir like: D:\IBM\WebSphere61\AppServer\profiles\AppSrv01\config\cells\machinenwb01uNode01Cell\nodes\machine01uNode01

“SOAP_CONNECTOR_ADDRESS”

<specialEndpoints xmi:id="NamedEndPoint_1245837904248" endPointName="SOAP_CONNECTOR_ADDRESS">
  <endPoint xmi:id="EndPoint_1245837904248" host="nsgshsjdnwb01u.news.newslimited.local" port="8880"/>
</specialEndpoints>

Installing updates to your integration server for JDE

put the PSFT_E1_Adapter.zip int o the dir below

D:\EnterpriseOne\wsg\IntegrationServer\replicate\inbound

deactivate your existing JDE package

Choose install inbound releases

Choose the zip file you just copied into the inbound dir

You should get success

Activate it

Then all your connections should still be in the list of adapters: